Database Info

[MOD][HOW TO] apps2ext for cm7 [link2sd + s2e + cMTD + eFOS]

Hi ^^
Like many of us I was having some concerns about moving away from cm6 to cm7. I was using firerat's magpie build of cm6 and LOVED it. My biggest concern was that losing a2ext is not an option for me as I have a ton of apps that I use only occasionally and don't want them taking up space on my internal memory. After looking around I found a couple of solutions that work extremely well together (so far). There was not nearly enough documentation in one place to get everything working out of the box, but hopefully this post will give you enough to get started. My solution involves using a modified version of cMTD by firerat and two apps available on the market or from xda: link2sd and S2E (simple2ext).
Background information:
Firerat's cMTD is a patch that you flash in recovery which allows you to control the size of /system, /cache and /data partitions. Using this patcher you can reduce the extra space left on /system by ~30mb, /cache by ~45mb, and increase the size of /data by the combined difference. I would suggest checking out an older post of mine (linked below) that discusses adjusting the threshold value for low space warnings if you decide to use cMTD as the threshold is a percentage value based on the size of /data. This means that the more /data space you have, the higher the threshold will be (ex: default for n1 is ~20mb, after cMTD modifications that increases to ~35mb).
Ennon's eFOS is a script that you flash in recovery which moves non-essential gapps from /system/app to /data/app, thus freeing up even more space on your /system partition. This *may not* be entirely necessary as the newest gapps archive is *much* smaller (~5mb) than previous versions and many of the gapps are available directly from the market. I'm including the scripts just in case anyone wants them.
Link2sd is a frontend for a script which manages the moving of apps to your ext partition (also supports fat) and creates syslink files in your /data/app folder which point to the app's actual location on the ext partition.
S2E(Simple2Ext) is similar to Link2sd, but instead of creating symlinks for individual apps it allows you to symlink entire folders to the ext partition. S2E may require an EXT flavor partition, but I haven't tried fat so I can't say for sure. I use S2E to move my dalvik cache and download cache folders to my ext partition freeing up even more space on internal memory.
Basic Method:
[a2ext ONLY]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. If you wish to recover additional space on your /system and /data partitions using FRcMTD and eFOS, see the Easy or Manual methods below.
Requirements:
+ cm7 rom
+ cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
Steps:
1. Download cm7-a2ext-installer-0.1.zip and move it to /sdcard/.
2. Reboot into recovery.
3. NANDROID BACKUP!!!
4. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
5. Flash cm7.
6. Flash gapps.
7. Flash cm7-a2ext installer from /sdcard/cm7-a2ext-installer-0.1-signed.zip.
8. Reboot into CM7.
9. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
10. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
11. Reboot to complete the S2E changes.
12. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
5. Reboot into CM7.
6. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
7. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
8. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Easy Method:
[a2ext + FRcMTD + eFOS]
----------------------
Description:
This method will install a copy of Link2SD and S2E(Simple2Ext) to /system/app, create the mounting scripts for an ext3 partition, and adjust your low space threshold value from 10% to 3%. It also includes optional steps that will enable FRcMTD and move less essential gapps from your /system/app folder to your /data/app folder.
Requirements:
+ cm7 rom
+ cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
Steps:
1. Download cm7-a2ext-package-0.1.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
13. Reboot into CM7.
14. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
15. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
16. Reboot to complete the S2E changes.
17. Congratulations! You should now have a2ext with cm7 ^_^
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. Flash cm7-a2ext installer from /sdcard/cm7-a2ext/cm7-a2ext-installer-0.1-signed.zip.
6. Reboot into CM7.
7. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
8. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
9. Reboot to complete the S2E changes.
10. Congratulations! You should now have a2ext with cm7 ^_^
Manual Method:
[a2ext + FRcMTD + eFOS]
------------------------
Description:
This is my original method and is more involved, but it contains all of the steps required to setup a2ext, move your cache folders, adjust your partition sizes using FRcMTD, and move gapps from /system to /data using Ennon's eFOS scripts.
Requirements:
+ cm7 rom
+ cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
+ root explorer, adb, or terminal access
Steps:
1. Download cm7-a2ext.zip and extract the contents to your sdcard.
2. [cMTD] Copy mtdpartmap.txt from the /sdcard/cm7-a2ext/cMTD folder to /sdcard/.
3. Reboot into recovery.
4. NANDROID BACKUP!!!
5. [optional] Wipe all data if installing cm7 for the first time (see the cm7 install instructions for more info).
6. [eFOS] Flash eFOS step 1 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps1-signed.zip
7. Flash cm7.
8. Flash gapps.
9. [eFOS] If you are using eFOS, flash step 2 from /sdcard/cm7-a2ext/eFOS/ennon-fso-gapps2-signed.zip.
10. [cMTD] Flash cMTD recovery from /sdcard/cm7-a2ext/cMTD/Recovery-cMTD.zip.
11. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip.
12. [optional] If you have access to adb in your recovery see the note about adb below.
13. Reboot into CM7.
14. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
15. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
16. Reboot phone.
17. From the market install Link2sd and S2E.
18. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
19. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
20. Reboot to complete the S2E changes.
21. Congratulations! You should now have a2ext with cm7 ^_^
Additional Steps:
22. [threshold value] If you are getting low space messages with ~30mb free space on internal memory, you should consider checking out my tutorial on adjusting the threshold value. The link is at the bottom of this post.
Updating CM7:
1. Reboot into recovery.
2. NANDROID BACKUP!!!
3. Flash CM7.
4. [cMTD] Flash cMTD boot from /sdcard/cm7-a2ext/cMTD/Boot-cMTD.zip
5. [optional] If you have access to adb in your recovery see the note about adb below.
6. Reboot into CM7.
7. From root explorer:
a) Navigate to /sdcard/cm7-a2ext/link2sd-config-scripts/ use multi-select on 11link2sd and 99complete then select Copy.
B) Navigate to /etc/init.d/ and select mount r/w from the upper right corner of the screen.
c) Paste the copied files.
8. Long press 11link2sd and select Permissions. Ensure that the permissions are set to rwxr-x---. Repeat this step for 99complete.
9. Reboot phone.
10. [Optional] Open S2E and enable the dalvik cache and download cache options. Moving applications are not necessary.
11. Open Link2sd (if you are prompted to select a partition type, see the link2sd note below. otherwise you should have working a2ext).
12. Reboot to complete the S2E changes.
13. Congratulations! You should now have an updated system with a2ext^_^
notes:
-------------------------
adb / terminal note:
If you have access to adb from your recovery, you can potentially avoid an extra reboot by copying the config scripts from /sdcard/cm7-a2ext/link2sd-config-scripts/ to /etc/init.d/ before you boot cm7 for the first time. I haven't tested this, but I see no reason that it shouldn't work. I'm not going to go into too much detail about terminal commands because I will assume that if you're trying this you know what you're doing and if you don't, you should probably just buy root explorer and save yourself the hassle.
cMTD Note:
As of this writing the current install size for cm7 nightlies is just under 120mb. If you install cMTD make sure that the values in mtdpartmap.txt allow for enough room to fully install cm7 or you will have issues. The current values are set to 125mb system, 5mb cache, and everything extra goes to /data. It should also be noted that cm7 dynamically detects the cache value and moves the cache location if the size is <20mb.
link2sd Note:
Normally when you start link2sd for the first time, it asks you to select your partition type so it can create a script to mount the partition at boot. The config scripts (11link2sd and 99complete) serve this function, so if you are prompted to create the script /sd-ext and /data/sdext2 have not mounted properly. This is probably due to a device specific configuration issue. The included files are for an ext3 partition. If you have a different flavor of ext, you will need to adjust the 99complete script accordingly. Also keep in mind that if you are using s2e, it does not yet support ext4 so use at your own risk.
default install location note:
Since you have gone through all this trouble, it might be pertinent to change the default install location to internal in settings > cyanogenmod settings > application > install location. This will prevent cm7 from installing apps to the native FroyoApps2SD, thus negating all the benefits of using a2ext in the first place.
updating cm7 note:
You should be aware that many of these steps will have to be reproduced every time you update cm7. This is due to the fact that cm7 overwrites many of the files you are installing when you update. Fortunately, you won't lose anything on your ext partition and things go much quicker the second time through. See the section updating cm7 above for instructions.
Links:
--------------------------
cm7-a2ext:
cm7-a2ext-package-0.1.zip - http://hotfile.com/dl/112853580/9b85471/cm7-a2ext-package-0.1.zip.html
cm7-a2ext-installer-0.1.zip - http://hotfile.com/dl/112853289/7d2e803/cm7-a2ext-installer-0.1-signed.zip.html
cm7-a2ext archive - http://hotfile.com/dl/112487448/8264b72/cm7-a2ext.zip.html
Apps:
Link2sd - http://forum.xda-developers.com/showthread.php?t=919326
S2E (simple2ext) - http://forum.xda-developers.com/showthread.php?t=917377
cMTD Stuff:
Firerat's cMTD - http://forum.xda-developers.com/showthread.php?p=7061471#post7061471
cMTD cm7 specific - http://forum.cyanogenmod.com/topic/17752-cm7-issues-with-cmtd/
patched cMTD for cm7 (original post) - http://www.teamuscellular.com/Forum/viewtopic.php?f=29&t=178
Ennon's eFOS:
original thread - http://forum.cyanogenmod.com/topic/...-cyanogenmod6-firerats-cmtd-ennons-fso-gapps/
other:
How to change threshold value - http://forum.cyanogenmod.com/topic/...n-space”-warnings/page__p__107672#entry107672
cross posted from http://forum.cyanogenmod.com/topic/19160-how-to-a2ext-for-cm7/

does this still work?

yes. i have successfully used it on every nightly for CM7 (that i happened to install) through to the current official build as well as the temasek "self kang" builds where available (http://forum.xda-developers.com/showthread.php?t=1421425).

thank you flashing will report bak in a while
---------- Post added at 03:22 AM ---------- Previous post was at 02:56 AM ----------
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.

maxesxp said:
i tired and it didnt work... it says
--Installing: /sdcard/cm7-a2ext/eFOS/ennon-fso-
gapps1-signed.zip
Finding update package...
Opening update package...
E:Error in /sdcard/cm7-a2ext/efos/ennon-fso-gapp
s1-signed.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.

icecreamisdrugs said:
Ah. Forgot about that one. I haven't used it in forever to be honest. The ennon thing is super old now. Try looking for a new version or just delete system apps manually using titanium backup, root explorer, the terminal emulator or adb.
Search the forums for help if you're not sure what to toss.
Click to expand...
Click to collapse
okay thanks anyways

Nexus1 S2E ext4 - individual apps?
maxesxp said:
okay thanks anyways
Click to expand...
Click to collapse
Hi, I've been following your posts - I have cm7.2 and installed S2E - it seems to just WORK without having to do all the flashing above.
.... I see that my ext4 partition has some stuff in it, but the free space still indicates that my space for apps is huge number to 190mb...
have a look at this screen shot
==

[MOD][SCRIPT] Super WIPE Script HTC One | Aroma GUI (upd.18/03/2015)

This tool will allow you to easily WIPE system, data (except /data/media), boot (kernel) and cache partitions directly from custom recovery.
Before using this tool you need to be sure you are using latest version of custom recovery (TWRP or CWM). The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE. I recommend to use TWRP 2.6.3.0 (for v1.0.2d) and TWRP 2.8.5.* (for v2.0.2) .
v1.0.2d will work for Intarnational version, GE, T_Mobile, AT&T but NOT for SPRINT DEVICE
and v.2.0.2 - for all version!!!
To use this tool please copy zip file to your phone and then boot into custom recovery and choose Install. Then browse to where you copied zip file and select it. Aroma installer will begin. Choose options you want to run.
What script does:
1. Wipe /cache partition (select in Aroma);
2. Wipe delvik-cache (select in Aroma);
3. Wipe /system partition (select in Aroma);
4. Wipe /data partition except /data/media (select in Aroma);
5. Format boot partition (kernel) and removes /system/lib/modules (select in Aroma);
/system/lib/modules
/system/etc/init.d/01-h2w
/system/etc/init.d/01-pwp
/system/etc/init.d/01-therm
/system/etc/init.d/01-blinkbuttons
/system/etc/init.d/01-f2s
/system/etc/init.d/01-f2w
/system/etc/init.d/01-f2ws
/system/etc/init.d/01-f2wt
/system/etc/init.d/01-p2w
/system/etc/init.d/thoravukk
system/etc/init.d/89elementalx
/system/etc/init.d/99elementalx
/system/etc/init.d/99elementalx~
/system/etc/init.d/99bulletproof
/system/etc/init.d/56zram
/system/etc/init.d/30sweep2wake
/system/etc/elementalx.conf
/system/bin/fstrim
/system/usr/keylayout/synaptics-rmi-touchscreen.kl
/sys/android_touch/sweep2wake
/sys/android_touch/doubletap2wake
/sys/android_touch/logo2wake
/sys/android_touch/pocket_detect
/sys/android_touch/logo2menu
5. Removes some system files from /data/media;
/sdcard/.android_secure
/sdcard/.bookmark_thumb1
/sdcard/LazyList
/sdcard/LOST.DIR
/sdcard/.data/footprints
/sdcard/.data/mail
sdcard/Android/data/com.android.providers.media
/sdcard/Android/data/com.google.android.apps.genie.geniewidget.news-content-cache
/sdcard/Android/data/com.google.android.apps.maps
/sdcard/.data/navigator/Data/Temporary
6. Check partitions for errors;
7. Create a log of work on internal memory card.
This operation will remove all your data except for /data/media.
If you wipe ONLY BOOT, then you must to flash new kernel and kernel modules too (/system/lib/modules)!
Make sure that you have nandroid backup and Titanium backup before a full wipe!!!
You must have new ROM on /data/media to flash after full wipe!!!
If AROMA Installer stops at 0%, then you must to press Power button and hold 15-17 seconds to reboot. Then go to recovery and start installation again. This will help you.
***Credits***
amarullz for his AROMA Installer Script.
mike1986 for his SUPER WIPE script for Android Revolution HD.
Venom Team for updater-script for ViperOne.
LlabTooFeR for his updater-script for Maximus.
***Download***
Super_Wipe_HTC_One_FULL_v2.0.2.zip - some updates from 18/03/15
Arhive:
Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB - some updates from 24/11/13
md5: 60cff28e4f5ec11e11c15e7d37c54d35
Enjoy!

Version for HTC ONE M9 (ONLY!!!!)
(Russian interface)
Download:
Super_Wipe_HTC_One_M9_FULL_v3.0.1_RUS.zip

Thank you! :good:

Excellent, i miss this scripts since DHD days Thanks mate...

@Golv - good job

i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?

Magpir said:
i want to wipe everything except the contents on my sdcard download folder > eg. downloaded roms for flashing in TWRP
what should i choose.
what is this script do is the same as wiping in TWRP recovery?
Click to expand...
Click to collapse
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...

Golv said:
You must select all of items then will be deleted data, system, cache the boot partitions, after that you can return back into recovery, choose Install and select rom to flash.
This script makes a wipe as well as in TWRP recovery. It's more convenient to use script for somebody ...
Click to expand...
Click to collapse
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?

Magpir said:
i dont understand what this script does is wipe more stuff than the standard TWRP recovery or what?
isnt wiping the boot partitions dangerous?
Click to expand...
Click to collapse
In TWRP all the same, except wipe of boot partition. And there is no partition format /data/media in this script.
Boot partition can be flashed into bootloader (fastboot usb) through:
Code:
fastboot flash boot boot.img
or through:
Code:
fastboot oem rebootRUU
fastboot flash zip boot.zip
(If you S-OFF you can put into zip 2 files: boot.img and android-info.txt, if s-on - signed firmware.zip)
or into custom recovery (zip).
It's dangerous to delete HBOOT partition! In this case - bricks. If you erased boot partition then you can enter into bootloader and recovery and restore all things! ...

so are u telling me that yr script is different from wiping in TWRP ?
So yr script dont delete Hboot partition?

Do not worry! :laugh:
This script don't delete Hboot partition!

so its safe to use?

I checked all items of script on myself. All safe. And if someone does not think before to do something, it is always dangerous!

Awesome, been using a wipe script for the galaxy nexus, great to have one for the One, thanks OP!

when i use this script.
checked all options and wipe.. no rom and no kernel on my phone?
flash now a rom without choose fullwipe in aroma..
why all my apps on phone, my own homescreen?
sent from my HTC One powered by ViperOne

Hopie, thank you! Try this version. Super_Wipe_HTC_One_FULL_v1.0.2d.zip - 2.66 MB An updated version in OP.

Молодец, @Golv. Так держать.
Great work! Thanks.

forgot to answer
with new version all ok..
ium think u know it ^^
sent from my HTC One powered by IronByte

works this script on android 5?

Hopie said:
works this scriot on androud 5?
Click to expand...
Click to collapse
Yes.

[SCRIPT][DUAL-BOOT][I9305] db

(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !

thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?

LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion

il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?

LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?

il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?

LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..

il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks

LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..

Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.

Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..

Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)

Abandoned.

il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?

LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this

il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method

LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.

il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks

+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)

+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom

[Guide] Step by Step Installation of Android Pie Custom Roms

Step by Step Installation of/Upgrade to Android Pie Custom Roms
Following this guide, you will lose all your data if haven't backed it up yet!!
Also NO USING GSI PIE!!!
Requirements:
- Twrp is already installed.
What you need:
- LineageosTWRP (Attached to thread)
- Custom Rom (can be found here)
- Open Gapps (Pico or Nano)
Only if Root is wanted: Chose either of them
Magisk(Recommended) or SuperSU
- A brain and a body
- The Knowledge that you will wipe your phone by doing this. Be Warned.
Installation:
1. Backup all the files that you have either by copying them to a usb drive ,a micro SD or your computer.
2. Check that all files are copied successfully and can be opened or viewed.
( Some apps have a cloud synchonisation feature, use it if you have it as an option since it is really helpful!)
3. Now, get your preferred rom, gapps and if wanted, your root method ready, also unzip the twrp file aswell.
Copy them to your micro SD.
4. Boot into twrp via adb or by using some app(root needed).
In Twrp, go into wipe option, then select change file system. Change file System to ext4.
4.1 Now use Twrp Reboot-Menu Option to reboot into recovery(twrp) again.
4.2 Wipe system, data, cache and dalvik-cache partitions using the Wipe option
5. Go into Install Option and Press on "Install IMG" , select pietwrp image and flash it. (The name should be lineagerecovery.img or something if downloaded via telegram)
(If you don't have it yet and are in the Lenovo P2 Telegram group, type #pietwrp in chat and make sure to safe it to your download folder. Otherwise it's also attached to this thread.)
6. Reboot back to recovery like you did in step 4.1.
7. Now install your rom and gapps.
8. Wipe cache and then reboot .
9. Setup your phone and Enjoy.
( For Root, reboot to recovery. Flash your Root Method, wipe cache and reboot)
Enjoy and thank your Devs
FAQ
Q: Instructions unclear, phone stuck in bootloop
A: Either do this:
Download this folder and use one of the two ".bat" files. Boot into Bootloader via Volume Down and Power Button. --
It will flash S048 Firmware of our Lenovo P2, after the flash-process is finished it will boot up on its own. Recommended: Do all the ota updates via ota app.
Or: Boot into bootloader, via adb cmd prompt use: fastboot boot lineagerecovery.img , then use reboot menu to reboot into twrp. Clean Wipe phone(Wipe system,data, cache and dalvik-cache Partitions) and try flashing your Rom etc. again.
Q: Instructions unclear, hardbricked my phone!!
A: Thaat shouldn't have happened. Did you screw up somewhere?...
Luckily you backed up your most important files!

[TWRP] TWRP 3.4-0-0 For Blu G90 G0310WW [MT6765][Android 10]

First released twrp for BLU G90 phone.
Whats working:
Adb
Mtp
USb-OTG
MicroSD
Flash Image
Mount System , Vendor, product (contents of SUPER).... mount allows reading the partitions, but was not able to write to them
Back-Up/Restore to/from usb (or micro sdcard).... Due to size of super.img needed to format card ext4
Logcat
Screenshot
Known bug:
**Solved with new tree file**--data decryption is not working, so not able to read or backup internal storage.--
Built with Minimum Manifest _branch 10.0 :
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
Kernel source :
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device Tree :
New
GitHub - mrmazakblu/device_PBRP_BLU_G90_G0310WW at TWRP
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Download :
Releases · mrmazakblu/device_PBRP_BLU_G90_G0310WW
Contribute to mrmazakblu/device_PBRP_BLU_G90_G0310WW development by creating an account on GitHub.
github.com
Old
https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW
Download : https://github.com/mrmazakblu/device_TWRP_BLU_G90_G0310WW/releases

ADB Sideload is also broken.

Shananiganeer said:
ADB Sideload is also broken.
Click to expand...
Click to collapse
Most likely due to no able to read/ write to /data there is no place to temp store the zip.
Working on alternative options at the moment, as I am having trouble getting build correct to make decrypt.
Alternative is a modified /vendor.img, so device is not encrypted. But this of course is less secure.

I reformatted /data so it was unencrypted, but still couldn't use adb sideload. I was able to use adb push to put files onto the phone, but that didn't end up mattering as without rw to /system I can't install gapps XD. I'll have some time this weekend to take a look at things and try and help debug the decryption.

Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.

mrmazak said:
Appearently, this build is only missing data decryption.
Spoke with TWRP maintainer, they said this is working as intended. Super.img partitions are not currently meant to be mounted as r/w.
After I asked about flashing GApps, I was informed that there might be changes to TWRP source to allow mounting as r/w sometime sooner or later.
Click to expand...
Click to collapse
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.

Ivisibl3 said:
so it may seem we are waiting on how to affectively be able to modify the dynamic partitions before we can see a fully successful root. I am fairly new to these things so might be looking at it wrong.
Click to expand...
Click to collapse
To modify it "live" yes maybe.
You can modify the extracted system, as I did , using linux mount, and flash the system back modified, just like a gsi rom.
But for root, can't say.

On the latest build, was able to mount /system r/w. And successfully change the contents of it.
The patches in twrp source is not finished yet, so normal zip installs are not coded. But using adb shell (or TWRP terminal ) seem to be working.
This New build to be uploaded on github device source, as release "test build 9"

I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Well, the first thing I'm concerned with here is , I'm not sure if THIS TWRP will work on the g90 pro.
But it might be possible. I was able to mount system as r/w on my g90 in TWRP.
You would need to fastboot flash --disable-verity vbmeta and vbmeta_system to prevent red state bootloader lockout.

Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.

Shananiganeer said:
Ok I've found one potential bug and have a question you may be able to answer. With your build of TWRP I cannot access fastbootd. Running adb/fastboot reboot fastboot just puts me back into recovery. To change images I've been doing the following:
1. Enter bootloader and flash stock recovery you provided in your other G90 thread
2. Enter fastbootd and flash the image
3. Re-enter bootloader and flash twrp
The question I have is, how can the super partition be increased? I tried to flash the LOSQ build with gapps, but the image is > half the size of the super partition. I want to take 1GB away from the userdata partition and add it to the super partition instead. Do I mount the stock super.img in Linux and modify it to be 5GB, adjust the partitions on the eMMC so the new img will fit, flash the new super.img from bootloader, and then go into fastbootd and flash LOSQ? Where does modifying BoardConfig.mk with the new size fit in? If you don't know or don't wanna bother answering that's cool, I've been doing some digging trying to get to the bottom and I'm just not understanding how to adjust the new dynamic partition scheme.
Click to expand...
Click to collapse
The stock /product partition is not needed in non stock roms. Google gsi flashing guide tells show to delete logical partition product.
Code:
fastboot delete-logical-partition product
This is probably what is needed.
Don't know about your plan to increase stock super.img. no idea about why you mention boardconfig.mk

This TWRP is before the patch for TWRP fastbootd, so it is not included. I have resynced source, and will see if new build works, or not. If it does will post new release.

I mentioned BoardConfig.mk because the size of the super partition is listed there, but you were totally right about the product partition and I was able to flash LOSQ+gapps after deleting it. Thanks for the assist, and your work on porting TWRP to this awesome device! Will continue to keep an eye on your work as TWRP finalizes their support for Android 10.

Will this work for the G90 Pro? My guess is not but figured I'd ask

KryptekKnight said:
Will this work for the G90 Pro? My guess is not but figured I'd ask
Click to expand...
Click to collapse
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.

mrmazak said:
I assume not. But if you send device stock recovery, I can try to bring it up. But cannot test it, I don't have the device.
Click to expand...
Click to collapse
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide

KryptekKnight said:
Would you be able to compile a Gcam pretty for this phone? I would be willing to supply you with whatever is within my means to provide
Click to expand...
Click to collapse
I have no idea about gcam

johnsag49 said:
I have the G90 Pro and would love to be able to edit the build.prop file... the phone has a ridiculously low number of volume steps for media, 7.
Is there any way to boot into TWRP temporarily and edit the file, just to see if that will increase the steps? (by adding ro.config.media_vol_steps=30 for example)
Click to expand...
Click to collapse
Sorry OP.....
I need to get 01 post of your topic to report on custom recoveries on the G90 Pro.
For new users, you should know about the Android 10 permission structure.
In TWRP or PBRP, through the File Manager, it is not possible to copy files to the superpartition. But you can copy files from the superpartition to the internal SD card.
Therefore, to modify files from the super partition, it will be necessary to extract the super partition and extract system-product-vendor to then carry out the modifications and repackage.
Using Havocv3.11 the volume issue dissapears...........

Well all, thanks to @lopestom , we may soon have a new device tree to build recovery from , and data decryption is working on first test img. New recovery would be pbrp instead of twrp.