Hello everyone
This is CWM-Zip script to repartition our N7100 to gain 1.9 GB more for user data partition.
This script is originally from http://forum.xda-developers.com/galaxy-s3/development/guide-extra-1-3-gb-user-data-t2762594 It’s for GT-i9300. Made by @forumber2 :good:. Thanks to him, without his easy simple script, I wouldn’t be able to port this script.
This is how Samsung partitioned N7100
{
"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"
}
After running the script
Please note that this script is not suitable to ROMs that require storing big files in CACHE and PRELOAD or HIDDEN, notably Official ROMs, as you can see that CACHE and PRELOAD got shrank.
I’m not sure if there are some custom ROMs that store files in CACHE and PRELOAD, so check the ROMs installation zip first before using this repartition script. Check by reading update-binary in META-INF and observing folder structure inside the zip file.
I’m using DN3 v5+ and it doesn’t store any files.
I checked Omega v29, it doesn't use PRELOAD to store files, even wiping it before install.
X-Treme v2.1 is safe to install, even wiping PRELOAD before install.
BIG UPDATE 1
For some ROMs like Phoenix ROM requires storing data to PRELOAD, but not CACHE.
Use partition script "Repartition_N7100_16GB_PreloadStockSize587MB.zip" instead of "Repartition_N7100_16GB.zip"
It will partition PRELOAD to size of Stock 587 MBs.
CACHE remains 100 MBs, and SYSTEM remains around 2 GBs. GAINED USERDATA FREE SPACE IS AROUND 1328 MBs.
If your ROM .zip installer doesn't store files in PRELOAD, use "Repartition_N7100_16GB.zip" instead.
FYI, Big CACHE partition is used to store official Samsung OTA updates file, if you are on custom ROMs, then you can’t use Samsung OTA updates anyway. Big cache partition is practically waste of free space, but it is still required for Google Play APK downloads. (Max Google Play APK size is 50 MBs) In fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version. This script will partition CACHE with size of 100 MBs. For any Google Play apps that are bigger than 50 MB, they will use expansion files called .obb to help, those obb are stored in "Internal SD Card/Android/obb".
Samsung Apps APK downloads sometimes can be seen large to something like 300 MBs, but these APK downloads are stored in "/data/data/com.sec.android.app.samsungapps/files" So it won't break Samsung Apps downloads.
PRELOAD or HIDDEN is used to store Samsung crap stuffs like ringtones, Wonders of Nature video, starter beautiful images, VODB folder that is used for S-Pen stroke recognition. When user make a factory reset, all data in internal sd card gets deleted, then stuffs in PRELOAD gets copy to internal sd card. That’s why after factory reset Wonder of Nature video comes back.
ALL USERDATA AND INSTALLED OS ARE GOING TO BE REMOVED, SO BACKUP FIRST!
So let’s get started. You will use "Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip OR in the attachment
1.Backup of course, if you don’t do System Nandroid backup, be sure to have ROM installer zip ready in external sd card, if you do Nandroid backup or Titanium Backup, make sure to back up to external sd card because this process will erase internal sd card too.You may backup your internal sd card to external sd card, USB-OTG, or Windows PC.
2.You need to use PhilZ Recovery, it doesn’t work with TWRP, TWRP lacks of “parted” binary required for repartitioning.
I personally used PhilZ Touch 6.25.0 on my N7100. 6.41.6 reported to work as well.
3.Install the ZIP and the script will run, after it finished, it will reboot recovery again.
4.We are not done yet, this script still has some bug that formatted partition can’t be mounted. You can see that you can’t mount some partitions or maybe all, weird.
5.We need to fix mount problem manually by go to Mounts and Storage, then format System, Data, Cache, Preload or Hidden one by one, then go to Power Option and reboot recovery once. DO NOT FORMAT BOOT, MODEM, STORAGE/SDCARD1 (external sd card).
6.We have repartition successfully. Now restore data, install ROMs.
How to restore original stock partition table.
You will need to do this if you want to install stock official firmware.
1 - Download "Odin3_v3.07_with_PIT_16GB_GT-N7100.zip" and extract it somewhere
2 - Download any stock ROM from sammobile.com or samsung-updates.com and unzip it.
2 - Open Odin, click "PIT" button and select " PIT_N7100_16GB_20121102.pit"
3 - Click "PDA" and select official ROM that you've downloaded
4 - Click "Start"
5 - After installation, phone will be stuck at bootanimation, don't panic.
6 - Pull out battery, boot to recovery (you can see some mount errors, don't worry)
7 - Select "wipe data/factory reset" in recovery menu
8 - Select "reboot system now"
I recently update 4.3 MJ5 to 4.4.2 ND3 bootloader via odin successfully, just to inform that after repartition, bootloader update still works. If it fails, make sure to try new usb cable. Mine failed first time because of bad usb cable.
See ND 4.4.2 bootloader here http://forum.xda-developers.com/showthread.php?t=2472270 CTRL+F in the thread and find bootloader.
For some people who curious how to output partition table in Terminal.
First you need to install "parted" binary to /system/bin/
parted binary is in attachment,
then use these command in terminal
su
parted /dev/block/mmcblk0
print
Also programs to show partition tables in Google Play can't show partitions offsets, but this command could.
UPDATE 15/10/2014
I found out that in fact, Google Play apk downloads are stored in /data/com.android.providers.downloads/files/, cache partition is used to store apk downloads in old Android version.
UPDATE 24/10/2015
I also uploaded a new partition script cwm-zip file for AOSP users that will repartition system to size of 1 GB, preload 15 mb, cache 100 mb.
This will gain 3 GB of more userdata space.
Please note that once you have repartition with Repartition AOSP N7100 System 1 GB.zip
You will not be able to install Touchwiz based ROM, Touchwiz based ROMs are bigger than 1 GB.
You will have to repartition again with Repartition_N7100_16GB.zip OR Repartition_N7100_16GB_PreloadStockSize587MB.zip, note that all userdata will be deleted.
Note that I personally don't use Note 2 anymore, but this script should work. It's just simple script editing from previous files.
1 GB system partitioning for AOSP/CM is not working as
psndna88, AGNI kernel maker, tests
"it seems we cannot change SYSTEM size, else the bootloader boots only into download mode"
Thanks a lot. I will try it later.
I did repartition my device about a year ago, but I did it manually and used parted program that comes with cwm recovery. The process is fairly simple if you are familiar with unixlike OS'es. The advantage of parted us that you can resize /system partition too (CM11 requires just 400 mb on /system, and default is 1800mb).
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
steff195 said:
I just tried it. It all went fine. Thanks!
My question is, can we have more space, or this is the max we can have?
I guess some space must be reserved though, so the phone can work properly.
Click to expand...
Click to collapse
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
great guide, will try
reminds me of the htc days when we could s off and flash various hboots to increase/decrease various partitions
so, this will accomodate all current custom roms ? edit - just read your warning to check : thanks:
ninekaw9 said:
Yes we can have just a little bit more space. You may try to shrink cache partition to 60 mbs, shrink preload to 4 mb. That would gain 54 mbs only. I configured cache and preload to be bigger than this for safety purpose. Maybe it will be use to store small files in the future. We also need to keep the number of partitions to be the same as stock one, else everything will malfunction. I still have no ideas what does OTA and TOMBSTONES do.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
steff195 said:
Then I'll just leave it this way. Don't want my phone to malfunction if I push this to the extreme.
Thanks again!
Click to expand...
Click to collapse
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Can we increase system partition???
I need more space in system......
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
Man, I tried via Philz 6.41.6, since it was recommended in OP. I usually use TWRP, had a nandroid backup of everything including Modem made with TWRP which I placed on external card.
Had the mounting problem after flashing script and rebooting recovery, but I manually solved them, as described in 1st post. Then reflashed TWRP and restored my nandroid from external card. Then also restored my internal sd files (music, games obb, etc) which I saved on pc.
I have no error, I have ND3 modem present, all fine, phone works as before. And 12.1gb total space instead of 10.4 which I had before.
Thanks again!:good:
ulkika said:
only a small problem, it does not format anything and says that there is no sim inside, I sincerely hope that you manage to solve the problem ....
also the modem is not installed ...
Click to expand...
Click to collapse
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Rickav said:
I saw your post on the DN3 V5+ thread which led me... Seems to be a great concept, especially considering that one of the first things I do upon flashing a stock-based rom is to delete most Sammy things on it.
I understand that you need Philz to flash this; will the latest V6.41.4 do?
Also, do you know of anyway to save all system settings so as to restore them later? I can backup apps and their data but not the stock system settings themselves.
Click to expand...
Click to collapse
steff195 used Philz 6.41.6, and it worked.
Well, DN3 v5+ update-script has the commands to delete Android Setting Database on install.
Because you restore data first, then flash DN3v5+ which triggering deletion of Android Setting Database.
So you have to backup android setting database using titanium backup before repartition, then restore after repartition.
Or after repartitioning, install DN3 v5+ first, then restore data using nandroid.
I also have weird problem after deleting Android Setting Database on DN3 v5+. New setting generated is really courrupted. It breaks home button, notification toggles expanding, lock screen, and much more. Everybody else seem to be fine of android setting database regeneration. Weird.
MBariya said:
Can we increase system partition???
I need more space in system......
Click to expand...
Click to collapse
Yes you can.
Extract my .zip script, then open the updater-binary with your favorite text editor, I prefer Notepad++.
Find these line
parted /dev/block/mmcblk0 mkpart primary 168MB 270MB -> CACHE
parted /dev/block/mmcblk0 mkpart primary 270MB 2417MB -> SYSTEM
parted /dev/block/mmcblk0 mkpart primary 2417MB 2432MB -> HIDDEN
parted /dev/block/mmcblk0 mkpart primary 2432MB 2440MB -> OTA
parted /dev/block/mmcblk0 mkpart primary 2440MB 15.8GB -> USERDATA
It is pretty easy to understand indeed, first number after word "primary" is the start offset of the partition, second one is the end.
You may change those number. But remember that CACHE partition must always be bigger than 50 MBs to store google play apk download. Google stated that google play apk max size is 50 mb, bigger than that will use .obb to help.
I recommend you to keep OTA size 8 MB, cause I don't know what it does.
HIDDEN can be shrink up to 5 MB I doubt. I suspect that shrink up to 4 MB can cause issue, I don't know if you set size for 4 MB, will it exceed minimum partition size required.
However, numbers in red can't be changed, they must be 168MB and 15.8 GB the same.
And do not change order of partitions, and there must be 5 partitions. You can't remove HIDDEN and OTA, else partition order and number will wrong, and I think a lot of things will break, including recovery.
After you modified the script. Zip them and put in your phone and flash! :laugh:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
ninekaw9 said:
How come your modem firmware is gone?
Have you try installing ROMs again, most rom installer will flash modem firmware.
My script doesn't touch modem partition at all.
Just partition cache and after that, see the partition table.
Click to expand...
Click to collapse
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
ulkika said:
philz_touch_6.41.6-n7100.zip.md5 but the problem is that not format data,i solve whith reinstall nd3 and after root and restore system but the patch is not functionally at my device.
---------- Post added at 11:50 AM ---------- Previous post was at 11:45 AM ----------
I do not know what happens because of it, I can not see the pictures because you do not know how to send to you but that happens on the screen while doing the second restart to do manually format the system tells me that the memory is not formatted.
then I tried to reinstall the old rom and told me that he could not find the modem, it does not restart no line present it tell insert telephone card ... in the end I had to reinstall ND3, before I tried it with the pit from you and given after but not without changing anything in the system memory space....
Click to expand...
Click to collapse
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
only an other question,i use x-treme rom 2.1 is possible that is the problem...
ulkika said:
only an other question,i use x-treme rom 2.1 is possible that is the problem...
Click to expand...
Click to collapse
I'm downloading it and will diagnose the installation file.
ninekaw9 said:
I am very confused with your language. After you used my script, did you go to "Mounts and Storage", then format SYSTEM DATA CACHE PRELOAD?
Click to expand...
Click to collapse
after reboot of first install, is impossible for me format prelod .system and cache....
ulkika said:
after reboot of first install, is impossible for me format prelod .system and cache....
Click to expand...
Click to collapse
Try this Philz Touch version. It is the version that I used to repartition on my device.
I'm still downloading your ROM, mediafire is quite slow today.
Related
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Good question ..............i think there is no answer for this question
rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.
Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??
it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?
Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?
I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.
the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW
m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.
Nice work, thanks i will add this soon, in the future bootmenu versions
m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.
Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
These are the steps you should take before loading a new ROM:
1) Download your new ROM and relevant supporting or needed files like modem, alternate kernel, etc., and place them on your internal SD.
2) Backup your applications, settings, messages, etc., with a backup tool like Titanium Backup, image specific backup tool, etc.
3) Boot into recovery and run a “wipe data/factory reset"
4) Follow the developers ROM loading instructions.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
Nothing else on your SD card (internal or external) outside of these directories is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them. Your external SD card and SIM do not need to be removed. The goal here is load a new or updated ROM in as much a clean environment that you can. Files left behind in these, especially cache and davlik-cache can cause some of the strangest problems. The kind that nobody can really resolve.
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The sd-ext partition is an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have APP2SD or data2ext enabled. It is popularly used on devices that have little memory allotted to the /data partition. A misfortune that in my experience, Captivate does not partake in. Still, users who want to install more programs than the internal memory allows can take advantage of this partition and use it with a ROM supporting this feature.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Disclaimer! I am not responsible for any damage you may cause to your phone or SD Card if you try to enable/use sd-ext.
To enable sd-ext in ClockWork Mod (ROM Manager):
Boot into CWM
Go to Advanced
Then to "Partition SD Card"
Choose an sd-ext size
Then choose a swap size, or not. Swap is just like windows' virtual memory. The system will use it when you're running low on RAM and use it as temporary RAM storage. This is where you'll probably see an increase in speed.
Just for fun I put sd-ext at 512MB and Swap at 64MB which is probably more than plenty for the swap. The swap will assist a little with memory and with the extra space I can move my apps over to it with a program like App2SD or in most custom ROMs nowadays just use the "move to USB" option in "Manage Applications". Titanium Backup will also move apps to SD for you and I'm sure you can find plenty more in the market.
You can also use a tool like Minitool Partition Wizard:
1. Open Minitool Partition Wizard
2. Delete Existing Partition from SDCard (Backup data first!!)
3. Create Fat32 Partition
Note: Set all partitions to PRIMARY (Steps 3 - 6)
4. Create EXT2 Partition (System) about 150MB-200MB depend on ROM
5. Create EXT2 Partition (Data) about 150MB-250MB
6. Create EXT2 Partition (Cache) about 50MB
Personally I don't see a need to do any of this on either of my Captivate phones though I have played with it on my DEV phone.
And since it does play a big role and needs to be cleared at times...
Davlik-Cache - dalvik cache is a program cache area for the program "Dalvik". Dalvik is a java based virtual machine that is the base for running your (.apk) programs. In order to make access times faster (there wasn't a JIT compiler installed by default until Android 2.2), the dalvik-cache is the result of dalvik doing a optimization of the running program/s. This optimization is kept so that it is then re-used every time you use your application/s. By default, davlik-cache is located in your /data partition.
No, I'm not looking for donations. Just trying to clarify things for some.
Great info, but a "guide" assists you in doing something, this is just straight info.
While I initially intended on writing it to guide flashers into the benefits of a wipe data / factory reset, and avoiding the myriad of strange issues experienced, I can see now where it can more construed as informational. Hmmm... maybe I'll add more to it or ask a mod to change the title topic for me.
Regardless, my hope is that some people get some benefit out of it otherwise I've only wasted my time.
Thanks, I've been wondering for a while what that actually did.
Great start for a guide that should clear the boards up a bit. I vote it to be stickied after adding a bit more info on backing up, partitioning the sd card, dalvik cache, etc.
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Cozmo1 said:
I put this short guide together because I tend to see a lot of confusion regarding what a "wipe data / factory reset" does to your phone.
When you perform a “wipe data/factory reset” the content of the following directories are deleted :
/data
/cache
/datadata
/sd-ext
/sdcard/.android_secure
/cache - This is the partition where Android stores frequently accessed data and application components to make these, as implied, respond much faster as well as faster to retrieve / access.
/datadata – This directory contains the library, database, user specific configuration files as well as log files for its specific application installed in the /data directory.
/data directory is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially restores it to the way it was when you first booted it, or how it was after your last custom ROM install.
If your ROM uses an /sd-ext partition on your SD card for data storage your /data directory is mapped to /sd-ext and wiping the /sd-ext directory will result in losing your data.
/sd-ext is used for apps moved to your SD card. Your Android OS runs natively in an ext format while your SD card has a fat32 format, which is used typically for USB storage devices, Windows computers, etc.
The folder named .android_secure is where apps are stored when you perform the "move from phone to SDram/SD card" operation.
Consider this, Apps2SD uses the fat32 portion of your SD card, which is obviously limiting because it isn't Androids native file system. However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.
Nothing else on your SD card (internal or external) is modified so it is safe to leave files outside of the above mentioned directories without fear of losing them.
If you plan on trying several different ROM's and/or updating your favorite ROM every time a new version is released you need to invest in an application like Titanium Backup or one that comes with your ROM if it's supplied with one. MIUI includes one that works extremely well. Performing a “wipe data/factory reset" after loading your new ROM and before booting into it should provide you with a smoother transition to your newly chosen or upgraded ROM. Having a standard backup and restoral process should help you enjoy it quicker too.
Click to expand...
Click to collapse
Here is something I keep in a word file to help answer what you are also trying to answer. It is a bit shorter and simplified but it may help to polish your thread for us simpletons.
Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them. It does this when you make a major change like replace the kernel/modem. Clearing the Dalvik cache will force Android OS to recompile the apps for the the new kernel/modem. This can take time on the first boot after clearing the Dalvik cache.
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons. You want to clear this out so it doesn't re-use the old cached data.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.
snowake said:
I think it is important to explain that a reset should not be done after flashing a custom ROM because it deletes the Dev's settings/data/non-system apps. Instead flashers should either reset after flashing back to stock or before flashing a custom ROM over the current custom ROM.
Click to expand...
Click to collapse
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
do u have more info about "format your SD card, or partition a part of it as a ext file system" or how to do that.
i have read someone format part of the sdcard (class 10)to ext 2 or 4,to make the write n read faster.is that what you mean.can u guide me to the right direction.thank in advance.
? ? ? about this......(However, if you format your SD card, or partition a part of it as a ext file system, you can trick the phone into thinking it's part of the Android OS native environment. This will allow you to move applications, widgets, even cache and davlik cache over to it.)
Cozmo1 said:
This actually makes perfect sense to me. I have modified my OP because of your input. Thank you very much, snowake!
Click to expand...
Click to collapse
I struggled with all of this my first first few flashes.
xpakage said:
...Dalvik cache is a place where the Android OS re-compiles the executable programs the first time to optimize them.
...
Also the main data Cache is used by the Android OS at run-time to write temporary files for specific reasons.
Manually clearing both caches allows the new kernel/modem to be installed in a "cleaner" environment. It's just preventative maintenance.[/I]
Click to expand...
Click to collapse
That is much more boiled down. I looked back at the "how to flash" threads and a couple good explanations on custom roms. None explain this that I found.
Cosmo, here are some more thoughts on misunderstandings I have had and seen posted. Like post above I pasted from my notes, so may be incorrect.
Bootloaders: Same for Froyo/Eclaire in both i897 and i9000 roms. GB requires new bootloaders, but i897 are apparently cross-compatible. However, issues seem to pop up on i9000 roms with GB i897 bootloaders. If flashing back to Froyo, use the full jf6 stock, not cezar's stock eclaire without bootloaders.
Using Tibu: If no useful data (i.e. Bookmarks on dolphin) then simply click data only when restoring user apps. Typically no issues when restoring user apps after switching Android versions. However, system apps should not be restored because of the rom customizations. Especially when switching to GB because it uses different directory structure. I do not seem to have issues when staying on same version and restoring foreground (user accessible) apps with data only or restoring green text color sys apps with Tibu as icon (i.e. Accounts).
Rom manager: really only need the app if flash to stock and need to flash rom directly from cwm. If so, then flash cwm (top button in menu) and choose phone. This places update.zip in /sd, which is opened after selecting "reinstall update" in stock recovery. Usually have to select it twice for it to work. This will replace ATT stock 2e recovery (blue text) with cwm 2.5 (froyo).
Voodoo color, lagfix, sound: must either be included in kernel. Lagfix simply allows user to format sd as ext4 (linux). Color balances display so less blue iodes are used and color is more realistic. Sound allows clearer sound through headphones through tweaks enabled in voodoo app. If sound is not in kernel then purchase voodoo pro in market and it will install it into the kernel (if rooted, even if stock).
Thanks for clearing that up!
- Aaron
Updated with more details.
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
snowake said:
Great guide. In order to clear
/sdcard dir I master clear it after flashing to stock. Is there an alternate method besides deleting dirs myself?
Click to expand...
Click to collapse
That is probably the safest way to do it within the phone itself. An alternate way would be to mount it to your computer:
In Windows right click the drive that was assigned to your internal SD card and then click on format. By default it'll most likely set you to Fat32 and if you click format it'll say its complete, but nothing will be deleted. Android being a Linux OS doesn't use fat. You can format it by choosing exFat, but by doing this...
!!!WARNING!!! be aware that you will lose everything on your internal SD card AND your external SD card.
Emphasis placed mainly for others that read this and might not know.
Safer and easier to do it within the phone.
snowake said:
Really, really useful. Had no idea partition options were available to this extent! Especially swap. By mini tool are you referring to Easus' program? I am definitely checking this out tonight. Thanks!
Click to expand...
Click to collapse
This one is from MiniTool, though I wouldn't be surprised if Easus owned them. I didn't investigate to confirm. You can get the free home edition of MiniTool Partition Wizard here.
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
littlewierdo said:
Very nice infos. Deserves a sticky, although, probably in a different thread.
Some information on what "Master Clear" in Odin would also be helpful - I have never trusted my phone to 'truly' clear everything on the phone, I have found the Odin Master Clear option to be much more complete.
It is a bit odd, I do this with my PC every six months, I back everything up and format the drive and start over again (after running Spinrite on all the drives) - I do this on / around New Years and again over 4th of July weekend and I decided this past weekend to also do the same with my smart phones (4 Cappies) and tablets (Ipad and 2 Android tabs) this past weekend.
It gives me that sort of squeaky clean feeling and seems to make my devices run smoother. Maybe its all in my head, dunno *shrugs*.
One thing I can say however, I have not had a hard drive go bad on me since I started the Spinrite thing 10 years ago (I still have an 8 GB hdd in my desktop that is working!!).
Click to expand...
Click to collapse
I can run some tests on Odin's master clear to confirm what it does. Initially I would believe it does the same as a "wipe data / factory reset", but testing should let us know for sure. I'll test it this weekend. Maybe sooner.
Awesome to hear that I'm not the only advocate for SpinRite and I still use it a lot though not every 6 months like you do. It's definitely worth having and using.
MikeyMike01 said:
Any decent update(r)-script will do this for you.
Sent from my Infuse 4G
Click to expand...
Click to collapse
I totally 100% agree with you, MikeyMike01. Unfortunately, not all update scripts are created equally Asides from teaching people how to script themselves or parse through it, a task I do not have the time or patience to tackle, this it probably the easiest and best way to have users try to avoid the many and strange issues posted that possibly / most likely could've been avoided by using the tools at their disposal.
On a side note... I didn't notice you got yourself an Infuse 4G. Congrats! How do you like it? I've been out of contract for almost a year now and wouldn't mind upgrading (my wife is in contract), but I haven't seen anything really worth upgrading to or that does something I really need/want that the Captivate cannot, atm. I haven't looked up any specs and reviews on the Infuse yet tho.
This thread serves as a guide to install both firerats and data2ext mods on a single rom and have them work simultaneously.
I do not take any credit for the creation of any files mentioned or attached, nor methods for the installation of each individual mod, nor roms, gapps, or otherwise mentioned content. All credit goes to those who created each mod, rom, gapps, and the methods for installing each individually. I only claim responsibility for my own research and the order and hierarchy of steps below that combine these incredible feats of development into a working system of internal storage expansion and space management.
Even though it is impossible to brick your phone using the guide below, I am not responsible if you break your device, because you have willfully chosen on your own to void your warranty by rooting your phone and installing the mods mentioned below.
To make firerats work with data2ext simultaneously, follow these over-detailed instructions EXACTLY. This is written so that anyone who has never held a smartphone in their lives can understand and do this right the first time, so those of you that know what you're doing, sorry about the length, but it should be pretty easy for you.
Note: I've uploaded some pertinent files from the following steps and added all links to all files needed so you don't have to go find them yourself. I did not include any roms, gapps, or the freespace app from the Play Store(just download from your phone, or from the link in step 6d). Links for all necessary files are in their respective steps below. The only links to a rom or gapps are for ICS. Otherwise you'll have to find and use your own downloaded roms and the correct gapps for your rom. If you would rather use the links below to download the files instead of using the ones I provided, be my guest.
I've updated this guide to make installation much easier and work with Sense roms!
Now on to the good stuff!!
Steps 1 through 7a are written for you to collect the files necessary, and to prepare your phone, sd card, and recovery for the correct method of installation of the collected files.
Steps 8 through 10 are to install the mods.
Preparation
1. Be sure to start from scratch!!! This means an UNPARTITIONED, FULLY WIPED sd card, fully wiped and rooted phone, and fully wiped recovery. Fresh file downloads for roms, gapps, and other mods you like wouldn't hurt either. If your phone is not rooted, go here, it's the best and easiest root method I've found.
1a. If you already have a partitioned sd card, insert it into your computer via a microsd adapter or other means(you cannot use your phone for this; it will not recognize that it's partitioned), delete the partitions and wipe the card using partition management software on your computer. I recommend EASEUS Partition Manager 9.1.1 Home Edition(Windows users only). If you use this program, after you delete partitions on your sd card, you will be left with unallocated space. Create a partition that takes up the entire unallocated space and set it as a Primary and FAT32 file system(remember, only do this to your sd card, NOT THE C: DRIVE!!!!).
2. Boot to recovery(hold down home, press and release power, then release home once recovery shows up)
2a. Be sure you have a recovery that supports flashing unsigned .zip files. If your recovery does not support flashing unsigned .zip files, flash a rom and then the corresponding gapps that are signed(cyanogenmod roms and gapps are the easiest way to go), boot into rom, sign in, download rom manager from Market/Play Store, open rom manager, flash clockworkmod recovery, and boot to recovery.
3. Make sure you are using latest 5.5.0.4 recovery, found here.
3a. If you are not already using the 5.5.0.4, flash the 5.5.0.4.zip in your current recovery(or follow the instructions from step 2a if you cannot flash unsigned .zip files) and reboot back into recovery.
4. In your new recovery, make sure you wipe everything, and go to advanced>partition SD card. Choose whatever size you want to have as internal storage(the 'M' means Megabyte, if you didn't already know...). I use 1024M or 2048M(i.e. 1Gb or 2Gb), depending on what mood I'm in, but it works with any of them. Then choose 0M swap size and wait for it to process.
5. Wipe everything once again(just to be safe), including sd-ext, and place your rom and preferred gapps on sd card, along with any other flashable modifications you like to use(I use the sd card speed boost, which can be found here. 2048Kb works best for my card, a 16Gb Class 4).
Note: For ICS users only! I use official, larger ICS gapps, found here(download the one next to 4.0.X, the link will be: '20120429'). The smaller gapps, as well as the current best ICS rom, can be found in whoshotjr2006's thread, here.
6. Make sure you have the latest firerats(1.5.8), which can be found here.
6a. Don't use any of the alphas or betas. Just 1.5.8. Download only the recovery-v1.5.8-CustomMTD_S.zip and boot-v1.5.8-CustomMTD_S.zip and place on sd card. Create a .txt file named 'mtdpartmap' and type 'mtd XXX XX'. These X's represent the size in numbers that you want your /system and /cache partition sizes to be, and therefore will not actually be used. See step 6b or 6c, depending on what rom you'll be using, for information on how to determine the correct partition sizes/numbers to use. DON'T KEEP THE X's IN THE FILE! REPLACE THEM WITH THE NUMBERS YOU WILL USE AFTER YOU DETERMINE WHAT YOUR /SYSTEM AND /CACHE SIZES SHOULD BE!
6b. For ICS users: If you are using the official, larger gapps, type 'mtd 190 60' into the text file and save to sd card. If you are using smaller gapps, type 'mtd 190 30'. Proceed to step 7.
6c. For Non-ICS users: To find out what numbers to replace the X's with in your mtdpartmap.txt, first wipe everything and install only the rom and gapps you'll be using this mod with. Then boot into rom, sign in, and follow step 6d. After you do this, however, you will need to repeat steps 5 and 6a, then proceed to step 7.
6d. You can download 'freespace' from the Play Store, which needs root access, and will show you the total size and space remaining for each of the /system, /data, /cache, /sdcard, and /ext partitions, so you can change the numbers in your mtdpartmap file to what you want the /system and /cache to be that best suits the rom you want to flash. The first number after 'mtd' is for the /system partition, the second number is for /cache. You can't change the /data, because it is dependent on what you set the system and cache sizes to, and will be set to what you partitioned the sd card to anyways. Also, keep at least a 5Mb allowance over what you need for both /system and /cache partitions as you will run into force closing problems if there is no breathing room, especially for the /cache partition.
7. The data2ext thread and .zip file can be found here.
7a. Download the unCoRrUpTeD_data2extV2.2.zip at the bottom of the post and place on sd card. DO NOT FLASH!!!
Summary of what should be accomplished after following steps 1 through 7a: You should now be using CWM Recovery 5.5.0.4, have a partitioned sd card, wiped everything, and placed the boot-v1.5.8-CustomMTD_S.zip, recovery-v1.5.8-CustomMTD_S.zip, unCoRrUpTeD_data2extV2.2.zip, mtdpartmap.txt, the rom and correct gapps, as well as any other mods you want to use onto your sd card. If all of this is true, move to step 8. If not, go back and find what you missed.
The Installation Process
8. Flash recovery-v1.5.8-CustomMTD_S.zip, then under mounts and storage, wipe /system, /cache, and /data in that order.
8a. Reboot to recovery(go to advanced>reboot recovery).
9. Flash rom, gapps, and whatever other mods you have or like, then flash boot-v1.5.8-CustomMTD_S.zip, then unCoRrUpTeD_data2extV2.2.zip, and reboot.
Note: the firerats installation thread for the HeroCDMA says to flash boot-v1.5.8-CustomMTD_S.zip after anything that changes the kernel specifications, but the unCoRrUpTeD_data2extV2.2.zip does not change these. The thread also says that adb is necessary to reboot; it's not. After wiping /system, /cache, and /data, just go to advanced>reboot recovery. It will work just fine, I promise. Newer recoveries don't need to use adb for this step.
10. Reboot immediately after signing in for data2ext to take effect.
That's it! You're all done! Set up your phone the way you want and start installing apps!
Summary of steps 1 through 10: By now, you should be using 5.5.0.4 recovery, have a partitioned sd card, have placed all necessary files, your rom, gapps, and other mods onto your sd card, flashed the correct files in the correct order and rebooted, signed in, and rebooted after signing in. You should now be looking at the home screen(or lockscreen) of your rom, and if you check storage from settings, you should see internal storage showing the size you partitioned the sd card to be in step 4.
Hopefully this wasn't too confusing...good luck!
If you have any questions, don't hesitate to post in this thread!
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Hammerfest said:
Thanks, great guide! Wish I had it back when I had my first experience...
Speaking as per my own experience:
I ended up using the latest Firerats (dunno if its an alpha or beta) since I found myself flashing different ROM's and ROM updates quite a bit, for me it didn't require the use of a boot flash, rom works fine for me (spare some thoughts on this?, maybe just not required for the Alpha/Beta as abandoned work)...
Side note:
If you dont want to download an app to flash from the market to find out the space your rom is going to use for /system (at least, and for fresh install only), simply unzip your ROM and GApps to the same directory and right click and view the properties, this is its uncompressed size, and using a 4Mb buffer my self (Id recommend 8Mb just to be safe for most), Its normally right on the money for SOD or Size On Disk...
Click to expand...
Click to collapse
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
goliath714 said:
What version of firerats are you using? And I agree with you about the unzip method, and would have included that, but I wanted it to be as easy as possible for people who don't know what they're doing, and usually, 'an app for that' is the best way to go. Not saying it isn't easy to unzip, check the size, and rezip, I just thought an app that checks it for you would have less possibility of confusion. It does make the process a bit longer, yes, but at least people don't have to mess with the file at all.
On my own side note: After the several hours spent writing, rewording, adding, changing, and moving things around in this guide, I'm pleased to say it's 100% complete. No further changes that I can see happening.
Click to expand...
Click to collapse
I think 1.59 alpha... after a system crash a few months ago, i havent had the need to re-bookmark the firerats mediafire folder... I really should, and seeing as most file share hosts are closing down or restricting free access to files I really should re-download and archive them... god knows how many things I have lost because of the MAFIAA fiasco's...
Yeah that might be a good idea. Personally I've never used any alphas or betas so I really don't have any input for them lol
Sent from my HeroC using XDA
Bumping my own thread...lets get some more views for this thing! If you haven't tried it yet, or have questions about it, or simply don't know what it does, send me a message or post on this thread! It's really a very useful mod for those of you that use or like installing lots of apps...
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Hmoobphajej said:
Thanks for the guide to this. The only problem I may seem to have is that when I follow all your steps at 11b this is what I get:
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p2s apparently in use by the system; will not make a filesystem here!
Is that correct? Or am I doing something wrong?
Click to expand...
Click to collapse
You have to unmout the partition first.
#Root-Hack_Mod*Always\=LTE
App2sd
Yea, I got that too, is it not working for you.
If not, add "/system/etc/init.d/40data2ext --enable" That made it work for me. Don't add "".
after reboot and the memory still hasn't change then go back in to terminal manager and add the above line and then reboot, should work then, never got firerats to play nice with the script, so i just use data2sd
laie1472 said:
I see no reason to use both scripts combined. The data2ext you can have 2048mb/2gb That should be more than enough space for all your apps. Although this is a good write up I see a lot of conflict with using both mods together. One or the other should do. I'd recommend data2ext. You can create a 2048 partition and it will run just fine on a class 4 or better sd. Anything lower and you might suffer glitches like screen freezing, apps missing,lock up's and reboots. If you have a stock sd or a higher capacity sd but without a class rating or class 2 then I recommend firerats mod. Also you could very well run both of these mods and have not one problem whatsoever so it just user experience and preference I'm referring to.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
goliath714 said:
That's all true, but the reason I combined both is to customize the /system and /cache partitions, while still allowing my 2gb data partition to work. This way I have control over what size I want each partition to be.
Click to expand...
Click to collapse
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
fforward72 said:
In step 11 you said to reboot into rom immediately after flashing data2ext2-v7.zip and open terminal emulator. But terminal emulator isn't preinstalled in my rom. Is it ok to install it from play store after I flash data2ext2-v7.zip or this is not right?
Click to expand...
Click to collapse
You can install from the market
Sent from my HERO200 using xda app-developers app
ajrty33 said:
You can install from the market
Sent from my HERO200 using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot!
laie1472 said:
You can still achieve that without the combination of both mods.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
How? The firerats mod allows you to change the /system and /cache partition sizes, but from what I can find, data2ext only applies the /ext partition to the /data partition to make the phone utilize the /ext partition as /data, and doesn't allow for modification of the /system and /cache partitions.
Updated
Edit: Updated again to fix minor wording issues and make links much prettier!
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Sent from my HERO200
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed".
Any ideas?
dankdank11 said:
Can I use twrp recovery on this firerats. Or is it only the provided cwm recovery ?
Click to expand...
Click to collapse
Firerats has nothing to do with recovery. It's about resizing partitions. Recovery functions on a level above, so whatever you do with firerats won't affect it. TWRP is a great recovery program.
Tux2609 said:
So I flashed this data2ext on my desire, the phone recognized my ext partition as internal memory, but, I can't install any apps, I always get the message "application not installed". Any ideas?
Click to expand...
Click to collapse
Try again. Go through the instructions verbatim, as outlined. I wouldn't deviate in any way.
Now it's time for the partitions :good:
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
/boot
/system
/recovery
/data
/cache
/misc
In addition, there are the SD card partitions.
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the kernel and the ramdisk. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. To learn more about this partition and its contents, see the ‘About Android Recovery’ section of our guide to ClockworkMod recovery.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
With this, we conclude our tour of Android partitions. Now whenever you install a ROM or mod that requires you to wipe certain partitions before the installation, you should be in a better position to know what you’re losing and what not and thus, you’ll know what to backup and what not.
[info] rom 101 and cwm error solutions
Hi guys .You all know me.
I have created this thread for the sole purpose educating every newbie and noob about ROM and it's components...
Here goes
Parts of a ROM
i. The kernel.
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki, Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit or when the soft button's LED gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
Click to expand...
Click to collapse
ii. The operating system.
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
Click to expand...
Click to collapse
iii. Core functions.
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices.
Click to expand...
Click to collapse
iv. Optional applications.
These are applications provided by the manufacturer to give the device even more usability. Things like the Amazon MP3 store, PDF readers, Corporate Calendar etc. allow you to do even more with your device. Remember - Droid Does
Click to expand...
Click to collapse
B. How is a ROM packaged?
In most cases a ROM will come packaged in a .zip file. The recovery image’s kernel (yes, it has one too!) has the ability to unzip and copy the contents into the correct place. Inside this zip file is a folder
Click to expand...
Click to collapse
ROM & IT's COMPONENTS + CWM ERROR SOLUTIONS
ERRORS encountered in CWM Recovery
.
What is CWM Recovery ?
ClockworkMod Recovery is a custom recovery for many Android devices. It is considered to be the most popular recovery for Android due to its easily-ported nature, and integration with ClockworkMod ROM Manager by Koush(Koushik Dutta). The easiest way to recognize it is by the printed name when it first starts, and the background logo of a gear and hat.
Click to expand...
Click to collapse
ERROR STATUS 6
This is usually caused by CR/LF EOL(Windows style End Of Line) in updater-script. Change it to LF EOL(Unix Style EOL) using Linux command: dos2unix updater-script, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse
ERROR STATUS 7
This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this.
Click to expand...
Click to collapse
We have been consistently seen and heard people facing error “Status 7″ error while trying to flash or install
custom ROMs or firmware packages on their Android smart phones or tablets with ClockworkMod Recovery. Many
of the users are nowadays facing this problem with CWM Recovery while flashing .zip files of modded or custom
Ice Cream Sandwich (ICS) or Jelly Bean (JB) ROMs on their devices. So, you have also downloaded a custom ROM,
placed its .zip file in your phone’s or tablet’s SD card, booted into ClockworkMod Recovery, selected – “install zip
from sdcard” and then chosen the .zip file of the ROM to get it installed on your device. But instead of getting
flashed successfully, if you are facing the issue mentioned below, then just keep reading this article to find out
what’s wrong and fix up the problem :
Finding update package…
Opening update package…
Installing update…
Error in /sdcard/custom-jelly-bean-rom.zip (Status 7)
Installation aborted
Click to expand...
Click to collapse
or the following error right after CWM recovery shows –
Installing update…
assert failed: getprop(“ro.product.device”) == “I9103″ || getprop(“ro.build.product”) == “I9103″ || getprop
(“ro.product.board”) == “I9103″
Error in /sdcard/android-4-1-1-ics-rom-latest.zip (status 7)
Click to expand...
Click to collapse
So, if you are facing any of these errors while trying to install the desired custom ROM package on your Android
phone or tab, then you may try a various things or steps which may turn out to be the workaround of this
problem. Here are a few tips to get this “Status 7” error fixed in ClockworkMod Recovery and flash the ROM
successfully on your device :
(1) First of all, make sure your device’s bootloader is unlocked. If it is already unlocked but you are still
not able to flash the ROM, then just extract the .zip file of the ROM into a new folder, find the boot.img file from
that directory and flash it up on your phone or tablet via fastboot on your PC.
(2) Make sure that you are having the appropriate Radio or Baseband version installed on your device which is
supported by the custom ROM you are trying to flash. Most of the ROMs requires the latest version of Baseband, so
just update or upgrade your device to the latest Baseband version and then try to install the ROM once again.
(3) Update your device to the supported / latest build of official firmware before trying to install the ROM. You can
do it from – Settings > About Phone / Device > Software Update.
(4) Make sure you are having the supported or required kernel installed on your phone or tab. If it’s not, then flash
a new kernel right away and try to install your custom ROM once again.
(5) Is the ROM which you are trying to flash really works ? Find out whether it is working for other users or not.
Click to expand...
Click to collapse
its seems great buddy. Great Info. But as I always say, make it readable. Means highlights heading & important informations.
Edit: Great.. You did it already.
If possible then try to collect the error list & solutions of CWM error. I have searched a lot but in the office I can't open such sites, due to ban at sites. :Crying:
kataria.vikesh said:
its seems great buddy. Great Info. But as I always say, make it readable. Means highlights heading & important informations.
Edit: Great.. You did it already.
If possible then try to collect the error list & solutions of CWM error. I have searched a lot but in the office I can't open such sites, due to ban at sites. :Crying:
Click to expand...
Click to collapse
Okay let me see brother.
Re: [WIP]ROM & IT's COMPONENTS + CWM solutions
To everyone
If you have any suggestions please tell me and I will try to add it. :thumbup:
Sent from my GT-I9103 using xda app-developers app
Re: [WIP]ROM & IT's COMPONENTS + CWM solutions
Nice one..
Sent from my GT-I9103 using xda app-developers app
Buddy, Status 7 Error became part of Status 6 in your above post ^^.
Change the Subject & remove WIP. Also, Add CWM ERROR SOLUTIONS instead of CWM Solutions.
Guys is this thread worthy of being a sticky ??? I fyes how to get it sticked???
kartiknnn said:
Guys is this thread worthy of being a sticky ??? I fyes how to get it sticked???
Click to expand...
Click to collapse
Contact MOD for sticky.
Re: ROM & IT's COMPONENTS + CWM ERROR SOLUTIONS
One of the best threads in sgr forum.. Quite informative for a person like me:thumbup::thumbup:
Sent from my Jellybeaned Galaxy Royale
For mmc
One more Suggestion:
Add two more Post just below to your OP post (ask MOD to add two Post via PM)
In 2nd Post(after OP 1st): add CWM problem & solution while removing the same from Post no 1
In 3rd Post(after 2nd post): Add the follow details:
List of mmc blocks with partitions. Means you can check/know that in which partition what is having.
For example: in mmcblk0p1 - /efs -> Means in Partition One, its has /efs folder.
/tmp ramdisk (null)
/efs ext4 /dev/block/mmcblk0p1
/system ext4 /dev/block/mmcblk0p2
/cache ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p6
/prebuilt ext4 /dev/block/mmcblk0p11
/misc emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p9
/emmc vfat /dev/block/mmcblk0p4
/sdcard vfat /dev/block/mmcblk1p1
I don't know much about this but Devs can make me correct.
asked jonny as soon as he creates the two posts I will do the same
thanks vikesh
Edit: Done
Recovery Issue
I am trying to run a recovery in CWM V 6.0.3.1 and here is what I am seeing.
Checking MD5 sums...
Erasing boot before restore...
Restoring system...
Restoring data...
Error while restoring /data!
Anyone know how to remedy this?
My device is a Samsung Galaxy NOte 10.1 and the backup file is on my external sd card.
The Apostle said:
I am trying to run a recovery in CWM V 6.0.3.1 and here is what I am seeing.
Checking MD5 sums...
Erasing boot before restore...
Restoring system...
Restoring data...
Error while restoring /data!
Anyone know how to remedy this?
My device is a Samsung Galaxy NOte 10.1 and the backup file is on my external sd card.
Click to expand...
Click to collapse
Buddy are you sure that your backup was not of TWRP?
if yes then it will not restore.
Or do one thing try restoring by putting the backup in internal storage.
If doesn't work then try a different and properly functioning recovery.
:thumbup:
Best of luck!
Sent from my GT-I9103 using xda app-developers app
Tha TechnoCrat said:
Buddy are you sure that your backup was not of TWRP?
if yes then it will not restore.
Or do one thing try restoring by putting the backup in internal storage.
If doesn't work then try a different and properly functioning recovery.
:thumbup:
Best of luck!
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?
The Apostle said:
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?
Click to expand...
Click to collapse
Buddy I am sorry to say that I don't have Note 10.1 . So if you could check out the Note 10.1 forum to see if someone else is having the same thing
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"
The Apostle said:
Any thoughts or suggestions?
Click to expand...
Click to collapse
I feel you should try this.See if you can take backup on internal sdcard or not.
The Apostle said:
Yes I am sure. I wasn't even aware that TWRP was an option for the Note 10.1. I ended up doing a full restore from the base ROM. Then I tried backin git up once I had my settings all dialed in. Here is what I see when I attempt to make a backup on my external sd.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•backinf up of systemn complete...
•backing up data...
•backing up of data complete...
•no /sdcard/ .android_secure found. skipping backup of applications on external storage
•.
•backing up cache...
•backing up of cache complete...
•no external sd-ext found. skipping backup of sd-ext.
•generating MD5 sum...
When I try and backup on the internal sd here is what I get.
•backing up boot image...
•backup of boot image complete...
•backing up recovery image...
•backup of recovery image complete...
•backing up system...
•error while making backup image of /system
Any thoughts or suggestions?
Click to expand...
Click to collapse
Have u checked ur memory space?
Thanks,
Disturbed™
? Sent from my Disturbed™ Galaxy S4 using XDA Premium 4 ?
||||||||||||||||||||||||||||||||||||||||||||||●●●●●●●●●●●||||||||||||||||||||||||||||||||||
Wait for my time, U gonna pay for what U have done. - Disturbed™
Disturbed™ said:
Have u checked ur memory space?
Thanks,
Disturbed™
? Sent from my Disturbed™ Galaxy S4 using XDA Premium 4 ?
||||||||||||||||||||||||||||||||||||||||||||||●●●●●●●●●●●||||||||||||||||||||||||||||||||||
Wait for my time, U gonna pay for what U have done. - Disturbed™
Click to expand...
Click to collapse
+1
Sent from my GT-I9103 using xda app-developers app
#________MK60.1-M432-UNOFFICIAL________#
DISCLAIMER
Android 6.0 MokeeOS BETA-001 MK60.1-M432-20190906-UNOFFICIAL.zip designed for UBI + UBIFS R11 max chinaphone board variant Q6_MB_V1.0 only, this software comes on an as is basis with no warranties or gaurantees of any kind.
this is the first ever version of Android 6 for a ubifs device please hit the thanks button if you like my work
SYSTEM INFO
This version of MokeeOS is LineageOS 13.0 source that has been rethemed by the Mokee Open Source Devs this is actual Android 6 and requires stock KK kernel 3.4.67 in order to upgrade
Build compiled from eMMC Micromax A102 HW source replacing everything necessary in order for it to run on UBI + UBIFS blocks using prebuilt kernel & pre modified boot.img containing a storage fix to make 4GB userdata partition through recovery,
FEATURES AND NOTES
• Build comes preloaded with nanogapps_arm_6.0 so no need for gapps installation.
• Build comes pre-rooted with lineageOS root which can be found in developer options.
• Internal storage is system reserved and is user inaccessible, only the sdcard partition is user accessible in which most of your /data is set to be stored so i advise 10GB or more SDcard size.
• you will see a corrupt sdcard in settings under storage this is the ext4 /data partition if you format this you will royally stuff things up so dont do it or youll need to reflash the rom
• you may notice that your device now appears as htc_a16ul or HTC desire 530 in other words this is strictly only to pass googles stupid new device verification this build contains 0% htc sources
• video codecs have been updated but please do note its still a TN display its still horrible but bearable now.
• camera has been interpolated for better camera quality
Clearmotion added to increase the video recordings quality and smooth out the choppy slow video recording
• Bluetooth is using full unmodified micromax drivers from the source if you have problems with it comment
• if you dont want a slow device use a decent class 10 minimum sdcard with a high read write rate, remember this is your /data partition i suggest 16GB minimum or more due to the memory transfer technology controller in the larger cards being much more stable than quite frankly sub standard 8GB class 10 controllers or lower, you get what you pay for dont stinge on the sdcard.
WORKING
• ril (single and dualsim)
• wifi
• bluetooth
• mtp,adb
• secure storage
• basic phone functions
NOT WORKING
• Offline charging animation does not work but still charges.
• Camera cannot capture pictures or video camera crashes this is an app fault use cameringo or footeej
• Screenshots do not work due to internal being currently system reserved and not user accessible
• File manager crashes when first opened after first boot after this is fine but still p**ses me off so will fix when after other major bugs are fixed.
• not a bug but will sit on bootlogo for a minute or two on first boot before triggering the backlight and playing the bootanimation be patient
FLASHING
• RUN A FACTORY RESET WITH YOUR STOCK RECOVERY BEFORE DOING ANYTHING.
• Unzip MMB29M*****.zip and load the scatter file into SP flash tool & flash my recovery.
• Insert a Clas (10) no lower SDcard into the device after flashing.
• Power on to my compiled recovery by holding the power + volume up buttons until the recovery screen displays.
• Go to advanced, select partition SDcard, select 4096MB, i recommend selecting 128MB of swap after as this will compress it into an actual block or ram setting it to 256MB may impede performance.
• Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below
• Once transferred flash back first recovery go to main menu, select wipe, run a factory reset first, then select wipe all data pre flash,
• Once complete go back to main menu, select mounts you will see a partition under /persist format it so it can wipe the old unused partition and create the persist partition.
• Select mount system after as recovery cannot mount system in script, go back to main menu.
• Select install, then from sdcard, select the .zip and select install,
• You will be greeted with an on screen aroma- installer i repurposed from 2012 which has been completely re written and Mokee themed by me, follow the steps on screen & wait for install to finish.
• Flash the boot.img patch straight after the flashing the rom.zip
• Reboot no need to wipe cache or dalvik
Welcome to Android 6 Via MokeeOS/LineageOS
#________________LINKS__________________#
Recovery for flashing MokeeOS UPDATED
https://drive.google.com/file/d/1vggA-qFjsej2BdacsHUqnFOBx-izrCzK/view?usp=drivesdk
Recovery for transfering rom to sdcard as usb daemon dosent work on above recovery
https://drive.google.com/file/d/1Xv49Qr9cZtH18EtkYwLO5NNcFrTvUtLh/view?usp=drivesdk
BETA-001
MOKEE MK60.1-M432-UNOFFICIAL-20190906
https://drive.google.com/file/d/1CTYHHmefFesOHAIwfb8eF_2QBgeZDp6G/view?usp=drivesdk
[PATCH] BOOTIMG 2019-09-10 patches will be merged with the next update so you wont have to flash a patch.
https://drive.google.com/file/d/1SWn6JAzCynwlub8NGBCZ6VrdGs1nC42_/view?usp=drivesdk
hi Matty
I receive an error message when I try to flash your recovery. ERROR: S_INVALID_ARGUMENTS (1002)
SiXtyNiNe said:
hi Matty
I receive an error message when I try to flash your recovery. ERROR: S_INVALID_ARGUMENTS (1002)
Click to expand...
Click to collapse
I just checked recovery and scatter on my end all is working properly,
What version of SP flash tool are you using also Are you taking the battery out and reinserting before connecting to the pc for flash thats an important one or youll get flash erros You could also try to rename the recovery file to recovery.img instead of it having a default of no file extension but i cant see that being the problem,.
If you still get the problem use the scatter file from cyanogenmod 11 rom partitions are the same as same device
Matty1993 said:
I just checked recovery and scatter on my end all is working properly,
What version of SP flash tool are you using also Are you taking the battery out and reinserting before connecting to the pc for flash thats an important one or youll get flash erros You could also try to rename the recovery file to recovery.img instead of it having a default of no file extension but i cant see that being the problem,.
If you still get the problem use the scatter file from cyanogenmod 11 rom partitions are the same as same device
Click to expand...
Click to collapse
my newly updated version is 5.1916.00 but the same did not work. now I flashed the recovery only, with the scatter file contained in the cyanogenmod 11 and it worked. I'll go ahead I'll let you know
SiXtyNiNe said:
my newly updated version is 5.1916.00 but the same did not work. now I flashed the recovery only, with the scatter file contained in the cyanogenmod 11 and it worked. I'll go ahead I'll let you know
Click to expand...
Click to collapse
Hey mate sorry for late reply im on australian time,
Cool glad it worked out for you ill edit the .zip and reupload with a new scatter for everyone else,
Ill be uploading a boot.img patch aswell as i forgot to take a voldmanaged path out in the fstab so you may of gotten stuck on the starting apps screen boot patch will be up soon im on it now
Links have been updated and have added a second recovery to transfer the .zip to sdcard as the usb storage daemon seems kaput on the installation recovery,
Boot.img patch has been provided flash straight after installing mokeeOS
Pictures of build
Matty1993 said:
Hey mate sorry for late reply im on australian time,
Cool glad it worked out for you ill edit the .zip and reupload with a new scatter for everyone else,
Ill be uploading a boot.img patch aswell as i forgot to take a voldmanaged path out in the fstab so you may of gotten stuck on the starting apps screen boot patch will be up soon im on it now
Click to expand...
Click to collapse
Thanks for your help! for now I have only loaded the recovery, because I did not have time to flash the firmware inside. I will try Monday morning because I am away from home ... again thank you so much.
hi Matty ...the phone is stuck at the "starting apps". ok I realized now that I need to install the patch...
ok all done after new flash. Everything seems to work but everything seems a little slow for now ... and anyway I always have the problem of absence of imei. is there the possibility of being able to rewrite it in the Vnand?
SiXtyNiNe said:
ok all done after new flash. Everything seems to work but everything seems a little slow for now ... and anyway I always have the problem of absence of imei. is there the possibility of being able to rewrite it in the Vnand?
Click to expand...
Click to collapse
Hey mate,
Sorry for late reply just seen your comment
Yeah mokee is deffo a bit slower than my CM builds you should of seen it before i made all the swap changes and tweaks to it though that was slow lol but if you logged into your google account at the setupwiz it may run somewhat slow for a little bit as it will be downloading and applying updates to google applications, if this is the case usually leaving it for half hour to download and apply updates then rebooting it to apply the changes usually does the trick.
And still no imei ?? thats odd all needed files to rewrite the imei for new build are contained in sec files and are flashed straight after permissions are set,
Ill take another look at the boot.img's initrd and add all the protect info into a singular init. File and set it to be imported instead of adding the protect info manually to each init at its designated stages and ill upload once done this should fix the issue hopefully.
Ive nearly gotten just normal LineageOS 13.0 working properly for release also finally got internal storage mounted now after emulating it just need to work out external storage mounting for external storage but if i cant figure that out ill just release it anyway as beta build as its still completely useable as it is and is much much faster than mokee from my beta testing today on the device so fingers crossed
Anyhow ill let you know once the new boot patch is up so we can hopefully get your rild and nvd working again.
New patch is up in the links on the OP
i corrupted my imei just to to make sure the patch will work for you and is all good should restore nvd no problemo now and give you back your imei number
if flashing just the patch dosent work factory reset then format system and reflash the rom then the patch but you shouldnt need to do all that tho
Also fixed is MTP, ADB & Secure Storage which is set to hold the encrypted data on the external storage
thank you so much for your support you are great! ... I try the procedure even if I missed a bit on the steps, I don't understand what I have to do first and what I have to do then ... anyway I try.
---------- Post added at 01:46 PM ---------- Previous post was at 01:17 PM ----------
for flahing the rom what recovery should I use? first or second?
I flash new and I have new imei! ...but something wrong because the phone tells me that the sd card is damaged, if the phone format the message fades, but anyway there is not in the mem section. and the internal memory is very little.
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
P.S.
the camera does not work. probably due to the sd card problem.
And if I switch off the phone it won't start up anymore! there is something wrong with my steps
SiXtyNiNe said:
I flash new and I have new imei! ...but something wrong because the phone tells me that the sd card is damaged, if the phone format the message fades, but anyway there is not in the mem section. and the internal memory is very little.
---------- Post added at 03:03 PM ---------- Previous post was at 02:58 PM ----------
P.S.
the camera does not work. probably due to the sd card problem.
And if I switch off the phone it won't start up anymore! there is something wrong with my steps
Click to expand...
Click to collapse
The damaged sdcard isnt actually damaged as per is explained in the OP the system is only saying its damaged as its expecting the sdcard to be in vfat partition format but as /data is now on the sdcard as ext4 this is why it states that,
Camera dosent work also as explained in the OP has something to do with the app download cameringo,
If you formated the sdcard then you will need to reflash the rom again or it wont boot back up as you wiped the ext4 partition from the sdcard, so partition the sdcard through recovery again then re install the .zip then the patch and remember dont format the sdcard or as per OP things will go very wrong,
Been looking for the flag that controls that message to have it not show up if i cant be othered looking for it i may just add a prop to disable it in the build file on next update strange though i have to say my LineageOS 13 build doesnt display the message but yet both are lineageos 13 source,
Glad the imei is back now though youll have a useable phone once you do my steps above
hey friend thanks! I'm having fun with your work ... ok now I understand that I don't have to format the sd card ... but is it normal that the phone then only sees the little internal memory left? then I don't understand the sixth step ... (Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below) why do I have to use the other recovery?
SiXtyNiNe said:
hey friend thanks! I'm having fun with your work ... ok now I understand that I don't have to format the sd card ... but is it normal that the phone then only sees the little internal memory left? then I don't understand the sixth step ... (Once complete transfer MK60.1-M432-UNOFFICIAL-20190906.zip to the VFAT sdcard partiton by using the second recovery in links below) why do I have to use the other recovery?
Click to expand...
Click to collapse
You should see that your /data partition in your settings under storage should be 3.7 - 3.9GB
the system will state that there is not enough memory for some things as internal isnt mounted under internal when the apps expect them to be internal
i had to repath all internal stuff to be stored on external storage hence how i got secure storage to be set to sdcard1 which is external storage also and both are vfat so was only thing i could really do atm i as i cant mount both internal and external storage as they both wont show up if i do
and i cant set just normal internal storage for use or the camera and gallery apps and what not that rely on external storage wont work,
hence why i megered everything to be set to the bigger partition, if you can see my dilema storage is tricky with these devices am trying to work out storage paths and symlinks to mount both but so far no such success as of yet ive managed to merge all storage asserts to a singular init so its easier for me to work with so i can get it to hopefully mount both sooner or later
hi matty. I have this situation right now (picture in attachment) but I can't install any apps. all stuck on download. and even putting the files on Vfat from PC, when I install everything it remains locked on "install". then if I open a download link from the browser, I have a message that says I don't have a sd card inserted.
SiXtyNiNe said:
hi matty. I have this situation right now (picture in attachment) but I can't install any apps. all stuck on download. and even putting the files on Vfat from PC, when I install everything it remains locked on "install". then if I open a download link from the browser, I have a message that says I don't have a sd card inserted.
Click to expand...
Click to collapse
Downloads files from browser and apps from play store on my end perfectly fine so thats strange...
Your data looks ok and is mounted and the system is recognising that the sdcard as mounted and in use from what disk info is showing also so not sure on why its not recognising theres no external storage available when thats the storage path i used for external and also merged for internal
Ill have another look into it see if i cant re create the issue to get it solved for you anyway
If i cant get it fixed on your end ive got an unreleased version of cyanogenmod 12.1 which is android 5.1 i also compiled for our Q6_MB_V1.0 but never released as id gotten a 6.0 build working the next day so if i cant fix storage on this then ill try om that as storage changes are differnt and more close to 4.4 varying some minor changes so will be easier to mount both until i get LineageOS 13.0 external storage fixed as its quite tricky with all the differnt partitiion fs's from /system which is UBIFS (unsorted block image file system) + UBI (unsorted block image) that ubifs sits on in which UBI also sits on its MTD flash media transition layer, then /cache is yaffs2 coverted from ubifs using the old [email protected] block with swap added and /data is now emmc ext4 format using a partition on the sdcard,
Mounting system so things would boot was the main problem i faced but as /data is on the emmc external card getting it to properly mount through fstab via vold is quite tricky as the system path is
/dev/block/platform/mtk-msdc.1/mmcblk0 with also 0p1 0p2 and a 288mb 0p3 i also made for the next update but if i use in the fstab
/devices/platform/mtk-msdc.1/mmc0/mmc* with
Voldmanaged=sdcard0,auto,emulatedsd it wont mount internal and stops mountinf sdcard1 which also uses /devices/platform/mtk-msdc.1 you probably dont understand all this but ill get there with it eventually i spent 2 years already learning everything about ubifs to build these newer versions of android as before i released this the only version of android to be found for a ubifs device was 4.4.2 KK which has major security flaws so i wont be quitting on it any time soon
# UPDATES
MokeeOS Updates have been held back for the coming week or two as i have far to many projects on the go and am now using windows based software to recompile for updates as my linux rig is dead your patience is appreciated.
My new LineageOS 13.0 build will be released in the coming days for everyone instead luckily i could pump that out before the rig blew
I can confirm that as of sunday both internal & External storage are now working properly on 13.0 and are mounted and user accessible,
appropriate performance tweaks have also been made for the device hardware.
All i need to do now is fix the camera and link will be posted here to the new thread.
Thanks