Related
Note: I consider this obsolete and recommend rusmod
Bugfix v3
Here's the latest bugfix for Dexter's 1.3 aka stock221v13. This includes everything from Bugfix v2 and adds:
Extended power menu that adds "Reboot" and "Recovery" (see thumbnail below for a screenshot)
Include conservative governor (c19932, nadlabak)
Tweak to improve SD card read performance (reverendkjr)
DO NOT APPLY THIS TO XAVWANTED'S OR KHALPOWERS ROMS
The extended power menu requires extensive modifications to the framework. This patch includes Dexter's 1.3 framework. Don't hose your phone! I can help port the menu to the other ROMs, but this can and will bork your stuff if you're not running stock221v3 (+bugfix updates are OK).
Instructions:
Read all the instructions
Save stock221v3-bugfix-3.zip to OpenRecovery/updates/stock221v3-bugfix-3.zip
Boot to OpenRecovery
OR menu > nandroid > backup > system > backup selected
OR menu > nandroid > restore > stock221v13 > system > restore selected
OR menu > apply update > stock221v3-bugfix-3.zip
OR menu > wipe dalvik cache
OR menu > reboot system
Download:
http://www.multiupload.com/MTCIACFSJN
More details:
https://github.com/downloads/Mioze7Ae/XT720-patch
Experimental patches for bugfix v3
Experimental patches are minimally tested.
Metamorph compatibility fix
Volume-down boot to enter fastboot
Bugfix v2
Summary:
Graphics/OpenGL performance tweak (xavwanted)
Media library tweaks (xavwanted)
memhack (khalpowers) moves dalvik-cache to either /cache or /sd-ext
By default moves dalvik-cache to /cache
Will use /sd-ext/dalvik-cache instead if it exists (see also "User control of /sd-ext" below)
minfree memory parameters tweaked
Parameters from AutoKiller Memory Optimizer database
http://andrs.w3pla.net/autokiller/list/currentType/378
http://andrs.w3pla.net/autokiller/list/currentType/591
Fix milestone overclock persistence
Autodetects ext2/3 (kousik)
ext2/3 partition is checked and possibly repaired on boot
Disable automatic apps2ext. Native Froyo App2SD is not affected.
See also "User control of /sd-ext" below
apps2ext used to be called app2sd before native Froyo App2SD (apps2fat) existed. Confusing!
Add support for Link2SD
See also "User control of /sd-ext" below
Adds Maps.apk and updates YouTube.apk
User control of /sd-ext through manual creation of directories
/sd-ext/app (move /data/app to /sd-ext [apps2ext])
/sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
/sd-ext/app-private (move /data/app-private to /sd-ext)
/sd-ext/link2sd (enable Link2SD 1.5.1 support)
apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Replaces /system/oc with modular scripts in /system/etc/init.c
See the README on github for more details. https://github.com/Mioze7Ae/XT720-patch
Installation
Download and copy stock221v13-bugfix-2_signed.zip to the /sdcard/OpenRecovery/updates directory
Reboot into OpenRecovery
"Nandroid > Restore" Dexter's stock221v13 system (restoring boot not necessary)*
"Apply update" and select stock221v13-bugfix-2_signed.zip
Wipe data / factory reset*
*Advanced users: If you've been running Dexter's 1.3 (stock221v13) with the previous stock221v13-bugfix-1.zip, then it should be possible to apply bugfix-2 cleanly over stock221v13-bugfix-1.zip without first restoring system if you haven't made incompatible customizations to /system. You can also probably just clear the dalvik-cache instead of wiping, but I recommend doing that manually if you've moved it to sd-ext.
Download
http://www.multiupload.com/E7NJ9H2F9C
https://github.com/downloads/Mioze7Ae/XT720-patch/stock221v13-bugfix-2_signed.zip
Experimental patches for bugfix v2
Experimental patches are minimally tested.
Conservative governor suggested by c19932 module from nadlabak (included in bugfix-3)
reserved
this post intentionally left not blank
Disable automatic apps2ext. Native Froyo App2SD is affected.
Click to expand...
Click to collapse
Do you mean unaffected or is Froyo Native Apps2SD not working?
3rdstring said:
Do you mean unaffected or is Froyo Native Apps2SD not working?
Click to expand...
Click to collapse
Yes. You are correct native Apps2SD is NOT affected by disabling the automatic apps2ext. Thanks for catching that quickly!
tried to apply over last 1.3 bugfix patch.... "installation aborted".
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
c_urbanek said:
tried to apply over last 1.3 bugfix patch.... "installation aborted".
Click to expand...
Click to collapse
It's kind of a Hail Mary. It did work in my testing and I just tried it again with success. One thing is the new patch is signed so it could also be that your zip got corrupted in download. I've gotten installation aborted messages when the zip was corrupt, but there are probably other ways for it to fail. The md5sum should be
Code:
a93cfa1d6ea73a4ee8ff6ec4afc72baa stock221v13-bugfix-2_signed.zip
smoki3 said:
I have installed it over the first bugfix. It works perfekly! Where i can see if it applied?
Whats is the diffrent between app2ext an link2sd?
Click to expand...
Click to collapse
If you can see a /system/etc/init.d/00_memfree file on your phone, the update was applied.
App2ext moves all apps to the ext partition. Link2SD lets you do it selectively. This isn't a tremendous gain on Froyo, because we have the native move to SD. One difference is that using app2ext apps will be available while the sdcard is being accessed over USB. Also widgets should work for app2ext. At one point I unscientifically convinced myself that app2ext was faster at loading apps than the native move. That said, I'm not currently using either app2ext or link2sd except when testing. I did a big app purge recently and combined with the memhack I'm not running out of space (yet )
Okay the patch works very good! I have more memory now and it seems like it is very fast now! Great work
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Tavinsky said:
Thanks for this new update.
I have installed the patch stock221v13-bugfix-1, means that the new patch stock221v13-bugfix-2_signed what I can get to the Updates folder and apply it without restoring the data from the factory?
Means that the Dalvik-cache will automatically be going to SD?
Still need to partition the SD?
What about applications that are currently in the SD, which were moved to app2sd?
Thanks!
Click to expand...
Click to collapse
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
If you did move dalvik-cache to sd-ext, then OpenRecovery doesn't know how to wipe dalvik-cache correctly, so you'd have to do that manually. If you set up dalvik-cache on sd-ext, then you probably already know how ways to do that.
It should not affect any apps that are on SD.
If I was really clever I would figure out how to make the update clear dalvik-cache on install... hmmmm.
By default, what bugfix-2 does is move dalvik-cache to a different partition inside the phone, not to the SD card. /data and /cache are two different internal partitions. /data is what the phone GUI calls "Internal memory", but both are internal.
Why do this?
Eclair 2.1 wasn't designed for JIT so dalvik-cache didn't exist. New in froyo 2.2, JIT creates a lot of data in /data/dalvik-cache (at least 50mb, often 70-80mb). To accommodate for this increased use of /data in the Korean Motoroi froyo, Motorola adjusted the partitions to take 50mb from /cache and 20mb from /system to grow /data by 70mb. Dexter's 1.3 is built off of the 2.1 kernel and partitions and we can't change Motorola's partitioning (because of locked bootloader). So we end up losing space from /data. What we can do is put dalvik-cache on /cache (the one Motorola shrank) instead. That's what the update does.
Moving dalvik-cache to sd-ext is different. If you did not do that while running bugfix-1 (believe me you would know if you did), then you should be able to just apply bugfix-2, select wipe dalvik and reboot (the first boot after wiping dalvik is always slow). It should find your apps. There is a small chance you will have to wipe data / factory reset. I cannot guarantee it will work in all circumstances but it's worth a try. Take a nandroid backup of system, data, cache before applying bugfix-2 just to be safe.
It should not affect any apps that are on SD.
Click to expand...
Click to collapse
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Tavinsky said:
Thanks for your prompt reply, I have the question of how to move the dalvik-cache, you told me that "Would you believe me know if you did", then I'm sure they did not. Then, after applying the new patch, how should I move that dalvik-cache?.
Click to expand...
Click to collapse
It should move automatically. You don't have to do anything
Tavinsky said:
Just to make sure, when making a backup nandroid, I mark all partitions, excluding Basband software, linux bootloader, logo and device tree? If something fails, with this new backup can restore the phone as it was after applying the ROM of Dexter's, and the data and preferences?
Click to expand...
Click to collapse
That sounds right. I can't remember exactly which ones can't be backed up. To undo trying the patch you need to restore System, Data, Cache (maybe), SD Data (possibly, if you have one). It doesn't hurt to get more. Just read the nandroid output carefully to make sure no errors happened.
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
c19932 said:
I did not apply your patch because I am not really running out of storage memory on my phone and seems like that's the main focus of this patch. Just want to drop by and say thank you for your work and the clear description of the changelog, instead of the typical "optimal performance" and "faster system and more internal memory" that other posters do
While I appreciate the work and contribution by all members, I surely hope they will also post a more clarified changelog like yours
Click to expand...
Click to collapse
Thanks. Maybe I should break the changelog into subsystems. That might make it easier to scan.
The main non-memory improvements over bugfix-1 is xav's egl.cfg which really does help speed up the interface considerably and is the secret sauce of the recent themed ROMs here. We discussed it on the main thread just after bugfix-1 was released and a lot of us adopted it, but it seemed too experimental to push out as a default at the time. I've been running it since then without a problem and forgot that not everyone has it. Since khal and xav have been including it in all their ROMs, I decided it was probably time.
I also get a little annoyed at having to dig out these basic improvements from mostly theme and app-choice packages, but it does hone my understanding of android . I try to not push these things immediately out of respect to khal and xav. There was enough complaining yesterday about how to remove a theme get a "fast" stock ROM, that I decided it was probably time. There really hasn't been too much innovation lately between the ROMs, it's mostly been theming. It's sad xav's selling his phone.
The big problem still remains RAM use. Tweaking the minfree parameters seems more of a band-aid than a fix. That seems to be universal across all the froyo ROMs. Something isn't right. Maybe now that the Milestone froyo is finally released we can get to the heart of the problem.
* /sd-ext/app (move /data/app to /sd-ext [apps2ext])
* /sd-ext/dalvik-cache (move /data/dalvik-cache to /sd-ext)
* /sd-ext/app-private (move /data/app-private to /sd-ext)
* /sd-ext/link2sd (enable Link2SD 1.5.1 support)
* apps2ext has priority over link2sd and overrides! It doesn't make sense to use both!
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
hellmonger said:
Mioze7Ae again i love you ...you truly inspire me... sorry to ask such a basic question but i thought that in /sd-ext the forlder should be named *example* dalvik_cach and not dalvik-cach i see you changed all the _ for - is that on pourpose?
Click to expand...
Click to collapse
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
fwals said:
hello Mioze7Ae:
I have upgraded the stock221v13-bugfix-2_signed.zip.Upgraded before tock221v13-bugfix-1.zip.This had little impact, right? The upgrade will also be saving it? Always charge the battery power ah
Click to expand...
Click to collapse
I think you are asking: Is it OK to apply stock221v13-bugfix-2_signed.zip on top of stock221v13-bugfix-1.zip? I'm 95% confident it is OK.
Mioze7Ae said:
It must be /sd-ext/dalvik-cache not /sd-ext/dalvik_cache. If you use the _ the boot scripts will ignore it. See line 37 in
https://github.com/Mioze7Ae/XT720-patch/blob/master/src/system/etc/init.c/10_sdext
Maybe I accidentally hit a shift somewhere previously and didn't proofread carefully. Sorry for any confusion.
Click to expand...
Click to collapse
No no sorry to bother you you trully rock!!!!!!!
Hi guys,
lateley I saw F2FS support in Nightlies changelog of CM12.1. Im using latest TWRP + CM12.1. So.. how to get there?
Do I need a custom kernel? What if CM13 will be released do I have to go back to EXT4 before and will this work without problems?
Do I need to fully wipe all my data or can I just convert without data loss?
Help appreciated!
Kind regards!
[Edit: ]
Should I convert every partition or just cache + system?
Looking at http://review.cyanogenmod.org/#/c/109990/4/rootdir/etc/fstab.qcom, F2FS is only supported for the data and cache partition.
CM12.1 for klte/klteduos supports F2FS, TWRP has options under "wipe" -> "advanced wipe" -> "fs options" -> "change fs" to format the partitions to use F2FS.
You should make a full backup and then change the fs type. Dont't forget to backup your internal sdcard as this is not included in the TWRP backup.
There's a nice howto: http://forum.xda-developers.com/xpe...rial-migrate-filesystem-to-f2fs-ext4-t3004755
Good luck!
Thank you very much!
I've made a backup of data and cache and tried to convert but TWRP won't let me change to F2FS as the option is missing. Do I need some custom TRWP or did I miss something as I am using the latest version. Also, if I change the data partition my userspace won't be touched, right? So the backup of my userspace which I can see when I plug my phone to PC is not necessary, just for caution, right?
Thanks in advance!
[Edit: ]
If CM12.1 has the F2FS options, the kernel should automatically support the new file system? In your link they say you need TWRP with mkfs.f2fs support, so I need to change something somehow?
ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/showthread.php?t=2777835).
Just changed my cache partition with it.
BTW, if you followed the howto, you should have read that you can also download the provided mkfs.f2fs and push it to the original TWRP recovery.
I think, you don't read and search carefully enough. All your questions are answered in this forum, you just need to invest some time.
meiser said:
ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/showthread.php?t=2777835).
Just changed my cache partition with it.
BTW, if you followed the howto, you should have read that you can also download the provided mkfs.f2fs and push it to the original TWRP recovery.
I think, you don't read and search carefully enough. All your questions are answered in this forum, you just need to invest some time.
Click to expand...
Click to collapse
Thank you, again!
I used the search function before, the problem ist that it's very specific as there are dozens of kernel and custom roms and I wanted to be on the save side as I really need my mobile. But you are right, the mkfs.f2fs problem should have been solved by reading better. So this is now solved!
Kind regards
ktoonsez' TWRP image supports F2FS (http://forum.xda-developers.com/show....php?t=2777835)
Click to expand...
Click to collapse
As i see it can't format internal storage. Is there any solution?
Hello, am new here so if I did something wrong please correct me OK
-presentation:
we all love running latest android versions and install big a** games like asphalt 8 and have all the Google apps that we love
But in Janice it's some kind of impossible to do all of that ( come on its only 4 years old!!)
As they say no impossible under the sun now you can easily increase system or data or what ever partition your want just by flashing a Lil file and without losing a single file
-Warning:
Me and XDA are not responsible for any soft hard leaks or what ever you are doing this by your self!!!
Make a full backup(system data boot) before starting..
DO NOT USE THIS FILE WITH ROMS THAT USE CACHE (CM10.2)
-Requirements:
1. Janice or Janice-p(not tested)
2. TWRP Recovery (Any Version)
3. The attached file
Instruction:
1. Download the repartition file
-rename the file with your favorite partition sizes like "lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip" which means 1gb system 2gb sdcard and the rest will go to data partition so you will be able to install more apps
2. Boot into TWRP and make a backup
3. Flash the repartition file of your desire
4. Take a nap or watch big bang theory just waste some time
5. When the script finish restore your backup and reboot
6. Enjoy your games or what ever
-Credit:
1. @Lanchon
2. @madkita
If you want a file with your own sizes just write or in comments and i'll do my best to offer it to you
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=0.0625+wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add '+wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Lanchon said:
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=0.0625 wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add ' wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Click to expand...
Click to collapse
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
madkita said:
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
Click to expand...
Click to collapse
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Lanchon said:
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Click to expand...
Click to collapse
Yeah thank you updated OP
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
TheSteve87 said:
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
Click to expand...
Click to collapse
In TWRP it will be around 500-600mb with compression
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip
Just rename the file to this and your will have 1gb system 2gb SD card and the rest well go to data if you want to edit a partition size for example the number 1 after system means the system will be 1gb and the number 2 in front of SD card means the SD card will be 2gb and max in front of data means the rest well go to data partition
Preload and fota are partition used in only stock ROMs and stock based ROMs so if you are running a custom ROM this will give you more space in the partition your set to max
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
TheSteve87 said:
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
Click to expand...
Click to collapse
Yup it works if your wanna check system download a small app called disk info
If you want 3gb on sdcard change the 2 number in front of it this will give you 2gb on data
DaksAnkit said:
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
Click to expand...
Click to collapse
Yup 100%
Make a backup first and when resizing all partitions will be formated to ext4 then restore your backup it will automatically format them to f2fs
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
DaksAnkit said:
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
Click to expand...
Click to collapse
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
madkita said:
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
Click to expand...
Click to collapse
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
also so i have to now restore my backup to get back to cm13 coz i am stuck at recovery ? any shortcut,like(flashing cm13 kernel) to go back to system as it was before or i have to restore the backup ?
DaksAnkit said:
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
Click to expand...
Click to collapse
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
madkita said:
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
Click to expand...
Click to collapse
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i just install my backup and that is it ? right !!
DaksAnkit said:
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i ust install my backup and that is it ? right !!
Click to expand...
Click to collapse
Yup just restore your backup and you're done ?
madkita said:
yup just restore your backup and you're done
Click to expand...
Click to collapse
alrighty then !!
:good:
I`ll post how did it go later in the thread .
you have a good day bro enjoy sunday .. cheers
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
TPD-21 said:
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
Click to expand...
Click to collapse
First make a backup with your cm11's kernel then flash cm12.1 kernel then flash the script and the kernel doesn't t care about your current rom so it should work every where
I just read about changing the file system to F2FS, I used the JDCTeam-20170408 ROM (where they mention this change as optional)
I made before my backups with titanium root
I formated my op2, changed the system, cache, data to F2FS, and flashed the rom and gapps
First I noticed that the system partition was changed to EXT4 again, but data and cache were F2FS.
After reboot used titanium the get my apps restored, and some of them worked just fine. But games, that required large data download, were not restored at all, they freeze and even I get the large files were downloaded, after a reboot or just closed the app they needed to download again the files.
Does it means the games dont have F2FS support? Is the ROM? Did I made something wrong? or maybe the data partition need to be EXT4 as system?
Anyone that can help me please
Hi, please give me logs in PM or through any other service.
how?
MZO said:
Hi, please give me logs in PM or through any other service.
Click to expand...
Click to collapse
Sorry PM? dont know how to do that. And logs, how can i get them. Sorry Im new in this kind of issues.
And thanks for the quick reply.
Use adb logcat or an app called catlog.
I thought id put together a thread with all my main tweaks and modifications to allow our device to perform better
lets start!
Decrypt
this ones an easy one - flash noverity and decrypt and you're on your way right?
i took this a step further and modified the boot.img for 4.7.6 to remove encryption and verity and added some mount flags
the flags ive added are:
noatime - noauto_da_alloc - nodiratime - data=writeback - barrier=0 - nobh
you can google to find out more information about these flags, but they all deliver top performance with minimal risk (possible risk: sudden power off may result in data loss)
How to
easy! *required /data to be formatted if you are not already decrypted
flash the modified boot image: https://drive.google.com/open?id=1WItoR1ifuCRYXwBvzBdis3hUnCftlUd-
format /data
flash supersu / magisk if you were rooted otherwise stay stock
if you want to flash a kernel you need to replace the fstab.qcom with the modified version (to do this open the kernel zip and paste over the fstab.qcom)
kernel fstab.qcom: https://drive.google.com/open?id=1XRI5EWwREnvxCVWrjY4FFu1PQs1bbUje
Disable journaling completely
my favourite tweak - disables journaling
How to
i like doing this before first boot but you can do it whenever really
ideally in TWRP
first, explorer /dev/block/
for every file you see in /dev/block you add tune2fs -O ^has_journal before it
so for example, if /dev/block has a file called sdd01
you will type: tune2fs -O ^has_journal /dev/block/sdd01 in TWRP terminal
and so on for sdd02 etc etc (or you can create a script to do this for you) it will not succeed on all blocks as some dont have this features.
DOES NOT WORK ON 5T FOR SOME REASON WILL NOT BOOT INTO OS AFTER THIS IS DONE
Misc tweaks
some other tweaks i have not tested to see if they're working on the 5T
but here they are
How to
Scripts (you can run on boot or on demand):
fstrim (requires busybox): https://drive.google.com/open?id=1MSqvVlOr59Y8y-3DiJ3Snms_rEvJWVzX
sqlite vaccum and reindex database: https://drive.google.com/open?id=1NcW33rvoInQPSx9w8RcQ__GC_5Vhv-6a
also requires this file in xbin: https://drive.google.com/open?id=1p2COCUjhiAaIjyZjV84EmvUgntp0_bdi
zipalign: https://drive.google.com/open?id=1wWyfoy6QuVCtwUUkI9TVrobNbv7Kset8
also requires this file in xbin: https://drive.google.com/open?id=1K25bOrA7eVUacHEVrHNN2At6D-Dnfgmi
mark disk as non-rotational,disable iostats, simple iomerges no hash lookup, rq_Affinity set to 2 - best for multitasking uses all cores to complete request instead of cpu 'group' : https://drive.google.com/open?id=1YJ5GHGqwl8tzxvRyEGYINPIp4zdHUgTd
Stock Boot 4-7-6
https://drive.google.com/open?id=1OQKJB9gRj2SG7WS9J-ucuUaWmqPn1gMl
Stock Boot 4-7-6 no flags, decrypt no verity
https://drive.google.com/open?id=1gXYYw7E2fzSRkh2J-1hZIS4EH34zeBPT
if anyone has any other tweaks they'd like to share ill be sure to add them in!
THIS WORK IS OPEN TO ANYONE FOR USE
FREE KNOWLEDGE FOR ALL​
Thank for the tips, could you post the boot img for 4.7.6 with out the flags being set.
freegame619 said:
Thank for the tips, could you post the boot img for 4.7.6 with out the flags being set.
Click to expand...
Click to collapse
updated OP
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
raptor2003 said:
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
Click to expand...
Click to collapse
in my experience decrypting makes the phone perform better (people will argue it makes no difference) but every time ive done it i notice improvement.
twrp is fine for reading the sdcard, decrpytion has its benefits but also drawbacks (easier to hack, etc) you can do the research yourself, but there are benchmarks showing the differences (mainly reads are affected)
if you're smart with your phone (i.e dont download suspicious stuff) you should be fine without encryption.
ive never had it on, except when i cant turn it off
raptor2003 said:
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
Click to expand...
Click to collapse
To run decrypted ROMs mainly. I see no other reason but im curious too
Since some ROMs can only boot if you are decrypted i guess it's that
Did a very quick lookup of that journaling business and it sounds interesting. Have you noticed much of a difference in performance on vs disabled?
virtyx said:
updated OP
Click to expand...
Click to collapse
I was mentioning about the boot img without the flags being set not the one without the encryption turned off.
freegame619 said:
I was mentioning about the boot img without the flags being set not the one without the encryption turned off.
Click to expand...
Click to collapse
oh ok sorry i thought you meant stock boot.img
updated.
showofdeth said:
Did a very quick lookup of that journaling business and it sounds interesting. Have you noticed much of a difference in performance on vs disabled?
Click to expand...
Click to collapse
definitely found better responsiveness with it disabled, and multitasking is much better
Can u help me to create script for disabling journal? I had 100 files on block folder ?
Oh and also, can I flash ur modified boot.img on 4.7.5? Because I haven't got system update to 4.7.6. it would be troubling me if I had to reflash the whole 4.7.6 rom since I had around 300 apps installed. Thanks before btw
andrizmitnick said:
Can u help me to create script for disabling journal? I had 100 files on block folder
Oh and also, can I flash ur modified boot.img on 4.7.5? Because I haven't got system update to 4.7.6. it would be troubling me if I had to reflash the whole 4.7.6 rom since I had around 300 apps installed. Thanks before btw
Click to expand...
Click to collapse
Shouldn't have a problem booting 476 on 475 but you need to test
virtyx said:
oh ok sorry i thought you meant stock boot.img
I am on OB1 oreo, encrypted, oreo compatible twrp, rooted with magisk 15.2, the boot image available here are for nougat, is it possible you can do it for oreo, or any help towards this, thanks for your help, Regards.
Click to expand...
Click to collapse
vtec303 said:
virtyx said:
oh ok sorry i thought you meant stock boot.img
I am on OB1 oreo, encrypted, oreo compatible twrp, rooted with magisk 15.2, the boot image available here are for nougat, is it possible you can do it for oreo, or any help towards this, thanks for your help, Regards.
Click to expand...
Click to collapse
when I get time I'll look for the oreo boot img
Click to expand...
Click to collapse
virtyx said:
vtec303 said:
when I get time I'll look for the oreo boot img
Click to expand...
Click to collapse
ok thanks mate, cheers.
Click to expand...
Click to collapse