Related
Hi guys,
Big fan of the forums. I just got a replacement fascinate because there were issues with usb and I'm not sure if it was related to tinkering with roms and kernels, and what not. I would like to know if there's a way to make an extract replica of the phone's software (system, kernel, modem, and whatever else there is) so that if for whatever reason I want to go back to stock I can use that back up, instead of using other people's ODIN files which were conflicting (DI01 and DH12 together). Thanks in advance. Best regards and happy new year!
System:
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Kernel:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
Also,
http://adrynalyne.us/?p=89
How about a complete package?
Thanks for that!!
How do I create a complete package.. modem,kernel, system, and recovery. A total backup if you will, that I could flash with odin.
Something similar to what you posted here.
Thanks,
CMSeeley
Thank you very much for this adrynalyne, as well as for your other many contributions on these forums. How come you don't include the modem or PIT files? Are those unnecessary? And what is the difference from this method versus the one from your other link (DI01package3.tar.md5)? I've tried that one before but I wasn't successful one of the times, or I think I just needed to do a cache clear then it worked.
If you only have time for one question I'd rather know about the modem (extracting/restoring) and the PIT file which I believe is for proper partitioning. I just want something that can just make my phone as if I picked it up from the store and unwrapped it for the first time. Thanks in advance.
-eeshuz
adrynalyne said:
System:
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Kernel:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
Also,
(won't let me post url because I haven't posted 8 yet)
Click to expand...
Click to collapse
Pit doesnt seem to do much in Odin that I've seen.
Modem cannot yet be extracted, because we do not know where it is. It is not on bml12.
Gotcha. So if the modem can't be extracted, and the whereabouts (I'm assuming bml12 is a partition) is unknown, how do the current modem files exist and know where to be flashed to? Also, I noticed on your personal site you don't include a modem file to be flashed. Is that because it is unneeded regardless of which kernel and ROM are installed and doesn't conflict with either? I'm really trying to learn the technical part of this because I believe my background of web development might be useful in contributing to the community so I just don't want you to feel that I'm wasting your time. Thanks again.
adrynalyne said:
Pit doesnt seem to do much in Odin that I've seen.
Modem cannot yet be extracted, because we do not know where it is. It is not on bml12.
Click to expand...
Click to collapse
Hello there, I've just discovered the insane amount of memory used by the system (like 2GB+). I've just discovered that the CM11 just uses 500+MB. And here popped the question: how can i shrink the partition and give the unused space to the sdcard0 partition? Is it possible to do it whitout loosing data?
I got S4 with the Snapdragon, CM11 Installer (i can always flash the snapshot if needed).
Then googling around i found few things not exactly easy to use (unfortunately I'm not a developer); while reading those things it popped in my mind "what if i flash another .zip from recovery? Will it broken the phone? What if I'll flash stock from Odin?"
So here am I, asking on to you guys Thank you for the patience
On the i9500 flashing the chinese pit file reduces the system size.
But again flashing pit files in itself is a big deal. It can lead to a hardbrick.
So basically its better to stay happy with what Samsung has given us
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
On the i9500 flashing the chinese pit file reduces the system size.
But again flashing pit files in itself is a big deal. It can lead to a hardbrick.
So basically its better to stay happy with what Samsung has given us
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Probably you're right but i want to dare
Lamba92 said:
Probably you're right but i want to dare
Click to expand...
Click to collapse
Haha unfortunately the chinese pit is for i9500.
Find a similar one for the i9505. I bet there would be none, or if there are @Lennyz1988 can help you
"If someone helps, never forget to hit thanks ? "
Weeks ago I wrote this in another thread:
I'm who discovered the way to repartition three STE devices (S Advance, Ace II and S3 Mini).
After any kind of test on my I9505 I can sadly say that it's IMPOSSIBLE to repartition.
-PIT files are signed, if we don't have that signature to sign the file we can't use custom PITs.
-Size of the partitions are specified by three text entries (six in HEX) in some offsets before partition's name.
-Signature is 48 blocks long (768 offsets) and it's at the very end of the untouched file. Modifying PIT through PIT Magic totally breaks signature (is no longer inside file) and simply copy-paste works only when you don't modify things of file. It's generated depending on file lenght in blocks, any character inside and partitions' size and names, modifying also a single value of an offset means that we require a new signature because previous one is no longer valid.
-Device has a PIT partition, flash filename is MSM8960.pit. Isn't showed in dev/block since it's protected and hidden, creating a Odin-flashable package and trying to flash doesn't work since flash ends fine but new PIT isn't sent to device.
-When you tick Repartition in Odin and choose a PIT file, rightly after you start to flash that file is compared to the one inside PIT partition, if aren't 1:1 Odin refuses to flash and Download Mode screen gives "Secure Check Fail: PIT"
-KNOX bootloaders (4.3-4.4) have eMMC write protection for partition table, there's also a GPT backup inside. If you try to repartition mmcblk0 using parted or fdisk in ADB, commands end fine but nothing changes. After this operation, partitions are no longer accessible by recovery but just restart your device and let the magic happen (partitions agian accessible, nothing changed).
-Theoretically repartition through parted is possible with a non-KNOX bootloader (4.2) since seems that doesn't have eMMC write protection for partition table and GPT backup. I can't confirm because I have last bootloader.
Click to expand...
Click to collapse
Inviato dal mio GT-I9505
@AntaresOne You're back eh? hopefully and finally. ?
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
@AntaresOne You're back eh? hopefully and finally. ?
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Not fully back but yes, lol
Inviato dal mio GT-I9505
Q&A for [MOD][TWRP][RECOVERY] Reclaim the whole free space of your system partition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][TWRP][RECOVERY] Reclaim the whole free space of your system partition. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Khaon said:
Hello,
many users complain that since lollipop their system partition size doesn't reflect the actual system of the block device. Therefore, they can not install some extra in this partition( busybox, big gapps packages,etc.).
This is due to the system image size specified when building the rom:
One of the parameter of your system partition(which has been hardcoded in some config file, I.e. BoardConfig) is its size, but if the block device(i.e. the part of your internal storage that will be mounted for the system partition)'s size that is mounted is larger than the system partition's size than you will loose some space.
Fortunately resize2fs executable allows to modify an ext2,ext3,ext4 partition size:
This package simply resizes your system size to match the size of your block device size.
It does not alter your partitions table just reclaim the unmounted space.
Instructions:
Boot on a twrp 2.8.x.y TWRP recovery
flash the package
Download :
https://drive.google.com/file/d/0B9kxrJw-dzUmNG12QkdaU3R4Ujg/view
Credits :
@m11kkaa from whom I took the idea
Click to expand...
Click to collapse
Hello,
It doesn't work on my fresh install of 5.1 (stock and on nexus 7 2012 wifi). TWRP says :
Code:
Error executing updater binary in zip '/sdcard/resize_manta.zip'
Error flashing zip '/sdcard/resize_manta.zip'
I've tried both with TWRP and with nexus root toolkit. I've redownload the zip. Still the same.
Any idea ?
carrion crow said:
Hello,
It doesn't work on my fresh install of 5.1 (stock and on nexus 7 2012 wifi). TWRP says :
Code:
Error executing updater binary in zip '/sdcard/resize_manta.zip'
Error flashing zip '/sdcard/resize_manta.zip'
I've tried both with TWRP and with nexus root toolkit. I've redownload the zip. Still the same.
Any idea ?
Click to expand...
Click to collapse
The binary is not static and it was built for nexus 10.
OK, thank you. I will search for another solutions.
Khaon said:
Can you confirm this is the path of your system partition's block device?
Code:
dev/block/platform/sdhci-tegra.3/by-name/APP
Click to expand...
Click to collapse
I have a Nexus 7 (2012) and can confirm that this is the path of the device:
Code:
[email protected]:/ # cat /proc/mounts
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1 0 0
OK I won't be able to edit now but if you open the .sh fi!e you will be able to hardcode this path instead of the one I put!
0.0mb system on Nexus 7
So I found this post which have the solution to this problem here;
http://forum.xda-developers.com/nexus-10/development/mod-reclaim-free-space-partition-t3029605
This does not currently work for the Nexus 7. Since I'm a new member here I cannot answer the OP personally, but if he sees this or anyone care to relay the information;
I can confirm that this is the correct path
Code:
dev/block/platform/sdhci-tegra.3/by-name/APP
//MarK
Khaon said:
OK I won't be able to edit now but if you open the .sh fi!e you will be able to hardcode this path instead of the one I put!
Click to expand...
Click to collapse
Okay so I tried to hardcode this path. Maybe I'm just extremely stupid, but I couldn't get it to work.
Still get the Error executing updater binary. I'm on TWRP 2.8.7.0.
MarkPersson said:
Okay so I tried to hardcode this path. Maybe I'm just extremely stupid, but I couldn't get it to work.
Still get the Error executing updater binary. I'm on TWRP 2.8.7.0.
Click to expand...
Click to collapse
If you are on twrp 2.8.7.0 you dont need this anymore , yu can from the wipe screen resize a system partition
Khaon said:
If you are on twrp 2.8.7.0 you dont need this anymore , yu can from the wipe screen resize a system partition
Click to expand...
Click to collapse
Oh. I had no idea.
I don't know if the N7 has too low memory, but this didn't help at all unfortunately.
I get the following info:
Present: Yes
Size: 639MB
Free: 0MB
Used: 639MB
Backup Size: 639MB
Tried both to Resize and Repair but to no avail. :crying:
MarkPersson said:
Oh. I had no idea.
I don't know if the N7 has too low memory, but this didn't help at all unfortunately.
I get the following info:
Present: Yes
Size: 639MB
Free: 0MB
Used: 639MB
Backup Size: 639MB
Tried both to Resize and Repair but to no avail. :crying:
Click to expand...
Click to collapse
I'm probably, no ... surely ... completely out of my depth, but is there any chance this was done intentionally to keep Bad Things(tm) from being put onto the system partition? It seems like a horrible oversight so I'm wondering if it was intentional. Of course if a hack was in a position to write the the system partition, then it is just as likely in a position to delete something to make room, but that might then be noticed.
Just something that popped into my head after all day cooking for the in-laws and now trying to decompress with some Nexus hacking
Both the script and the TWRP functionality worked fine on my N10. But it still doesn't leave much space on /system when running a Marshmallow-based ROM. Meanwhile, I have 22GB free on my internal user storage (emulated SD card).
I'm curious if it would be possible to shrink that user partition size some and add that space to /system using this script or TWRP? Running fdisk -l /dev/block/mmcblk0 in adb shell shows only one partition, so I'm not totally sure how things are being sectioned off internally.
I used this for the main reason to fix the issue of insufficient space in system partition that wasn't letting me install gapps, I don't know why but after I did the mod, and flashed aicp is showing 700mb total on system partition in tibu, I thought it's supposed to be 800mb on it, no biggie since I fixed my main issue but I only have 13mb left in system.
Sent from my Nexus 10 using Tapatalk
PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.
I have a Eonon GA2114 (Android 4.4.4 RK3188 KLD) ROOTED car stereo.
I have searched this forum and cannot find what I am looking for so hoping someone can help or point me in the right direction?
I don't have many apps installed, but it seems as though the latest updates to Google, Maps, Sygic, etc. has resulted in an "insufficient storage" alert. I am quite happy with the stock ROM and don't really want to update to some of the custom ROMs that are available, but I do have a very technical background and have only ever owned Android devices.
Does anyone know or can point me towards instructions to change the system partition size? The system ships out with more than 8GB of internal space that I do not use and so would like to either repartition to a single large partition or reverse the size.
Thanks
I think you mean the /data (userdata) partition, and i'm pretty much in the same seat.
Got a brand new 16gig device that ships when a lousy 1gig of /data to store apps on, talk about drunken monkeys making the rom
got about 10 gig on the internal_sd that i'm guessing could be used instead.
I might try to remap that later, i guess you could root it and then either make a symblink there or look at the fstab and see if you could just remount it.
Could also flash Malaysk rom with gives you 2 gigs of userdata, not much more but alot better than 1gb
Yes, I mean the /data (userdata) partition and I checked, while driving to work, I actually have 13GB of userdata. I haven't used this space, but knew it was there when exploring the system when I first got it and for some reason I remembered 8GB. Regardless of the size, it's a waste of space if not utilised.
The system is already rooted.
I have considered Malaysk ROM, but I quite like the stock ROM, especially after installing my preferred launcher. I have already decreased the dpi from 240 to 180 so a lot better looking and a lot more screen space. Have got rid of bloat and so have a stock ROM to my liking.
These systems are well known for their mic troubles and I have taken this up with the manufacturer as I do work in the computer industry, but identifying electrical components and soldering is not something I am too confident with. The manufacturer did however, send me an updated update.img file. I've installed this and it made some improvement, but nothing so significant that I have actually started using the mic. It also has a new wallpaper and noticed that the default apps have been updated, but not sure how?
Anyway, if I don't like Malaysk I can revert back using the update.img file the manufacturer gave me, but 2GB still isn't enough. Hence, wanted to know how to do this myself.
Found this post: http://forum.xda-developers.com/gal...od-increase-partition-size-t3011162?nocache=1 by gsstudios
Obviously, connecting my system to a PC is not as easy and was wondering if anyone would know a bulletproof method of applying the instructions to my system given that it is a stereo with different hardware to a phone?
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
I also found a way to choose where the apps get installed, google a bit for "adb shell pm set-install-location" I belive #1 would be the right choice here.
If that works to redirect everything to the big partition it would be a wonderfull solution.
Download a terminal for the rom and type in there instead of having to connect a computer to the HU etc etc.
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
I would prefer rickthecabbie's solution, but in order to unpack the IMG file, I would need a Linux system (I have tried on Windows and couldn't do it). If all else fails, I'll dual-boot my PC or get a VM if that works? I would be really grateful if you can point me towards a tutorial/instructions if you know any or get the time, but appreciate your help as at least I've got somewhere to start my "Googling"
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
lotherius said:
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I asked the guys I bought the stereo from; if they had released an updated ROM or if they can provide me a download for the existing ROM. Their customer service so far, has been excellent; their English is not great and it can take a little extra time sending and waiting for messages, but they gave me a link.
At least, I know that if I mess things up, but haven't bricked it, I have got something to revert to.
You could try asking the seller/manufacturer for a link to the stock ROM?
rickthecabbie said:
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
Click to expand...
Click to collapse
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
tariqkhan.co.uk said:
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
Click to expand...
Click to collapse
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Hey rickthecabbie, that would be awesome.
Do you have the parameter file by any chance?
I recently made a change to the screen density. I have an 800x600 system and you can only fit 2 rows of icons across the screen so changed the build.prop file to 180dpi and now it looks much like a normal tablet. Having restored the system after making this change; it restored with my changes to the build.prop file intact. I was thinking, could I possibly do the same? I can modify the parameter file using ES Explorer/Terminal and then restore the system, which should update the partitions?
Saves on all the packing and unpacking and mainly; installing dual-boot/debian on my Windows PC.
tariqkhan.co.uk said:
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
Click to expand...
Click to collapse
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
treech said:
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
Click to expand...
Click to collapse
Yep, thought it would be something simple. Do you know of a command which would print which partition 0 and 1 and 2 is?
Don't really want it to set the install location to a partition that I wouldn't want it set to. Also, some apps are not movable so I don't think this would solve the issue right?
Not sure, you'll have to google it
And well best is to install a few bigger apps and see what happens i guess.
rickthecabbie said:
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Click to expand...
Click to collapse
I don't mean to bug you and do appreciate the advice so far, if you haven't got time to do the tutorial, do you know of a link to an existing tutorial?
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
jbleasdale said:
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
Click to expand...
Click to collapse
Thanks for the link.
Gave it a go and didn't work for me; I'm sure I've made a simple mistake somewhere although I tried twice.
As my system had already been wiped, I thought I would give DSA ROM a go and for anyone looking for a stock ROM, this is perfect. Any MODS included are a necessity in my opinion and some you will probably not even notice, but it has the 2GB system partition.
Hello, am new here so if I did something wrong please correct me OK
-presentation:
we all love running latest android versions and install big a** games like asphalt 8 and have all the Google apps that we love
But in Janice it's some kind of impossible to do all of that ( come on its only 4 years old!!)
As they say no impossible under the sun now you can easily increase system or data or what ever partition your want just by flashing a Lil file and without losing a single file
-Warning:
Me and XDA are not responsible for any soft hard leaks or what ever you are doing this by your self!!!
Make a full backup(system data boot) before starting..
DO NOT USE THIS FILE WITH ROMS THAT USE CACHE (CM10.2)
-Requirements:
1. Janice or Janice-p(not tested)
2. TWRP Recovery (Any Version)
3. The attached file
Instruction:
1. Download the repartition file
-rename the file with your favorite partition sizes like "lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip" which means 1gb system 2gb sdcard and the rest will go to data partition so you will be able to install more apps
2. Boot into TWRP and make a backup
3. Flash the repartition file of your desire
4. Take a nap or watch big bang theory just waste some time
5. When the script finish restore your backup and reboot
6. Enjoy your games or what ever
-Credit:
1. @Lanchon
2. @madkita
If you want a file with your own sizes just write or in comments and i'll do my best to offer it to you
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=0.0625+wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add '+wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Lanchon said:
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=0.0625 wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add ' wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Click to expand...
Click to collapse
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
madkita said:
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
Click to expand...
Click to collapse
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Lanchon said:
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Click to expand...
Click to collapse
Yeah thank you updated OP
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
TheSteve87 said:
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
Click to expand...
Click to collapse
In TWRP it will be around 500-600mb with compression
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip
Just rename the file to this and your will have 1gb system 2gb SD card and the rest well go to data if you want to edit a partition size for example the number 1 after system means the system will be 1gb and the number 2 in front of SD card means the SD card will be 2gb and max in front of data means the rest well go to data partition
Preload and fota are partition used in only stock ROMs and stock based ROMs so if you are running a custom ROM this will give you more space in the partition your set to max
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
TheSteve87 said:
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
Click to expand...
Click to collapse
Yup it works if your wanna check system download a small app called disk info
If you want 3gb on sdcard change the 2 number in front of it this will give you 2gb on data
DaksAnkit said:
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
Click to expand...
Click to collapse
Yup 100%
Make a backup first and when resizing all partitions will be formated to ext4 then restore your backup it will automatically format them to f2fs
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
DaksAnkit said:
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
Click to expand...
Click to collapse
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
madkita said:
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
Click to expand...
Click to collapse
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
also so i have to now restore my backup to get back to cm13 coz i am stuck at recovery ? any shortcut,like(flashing cm13 kernel) to go back to system as it was before or i have to restore the backup ?
DaksAnkit said:
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
Click to expand...
Click to collapse
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
madkita said:
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
Click to expand...
Click to collapse
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i just install my backup and that is it ? right !!
DaksAnkit said:
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i ust install my backup and that is it ? right !!
Click to expand...
Click to collapse
Yup just restore your backup and you're done ?
madkita said:
yup just restore your backup and you're done
Click to expand...
Click to collapse
alrighty then !!
:good:
I`ll post how did it go later in the thread .
you have a good day bro enjoy sunday .. cheers
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
TPD-21 said:
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
Click to expand...
Click to collapse
First make a backup with your cm11's kernel then flash cm12.1 kernel then flash the script and the kernel doesn't t care about your current rom so it should work every where