[MOD / TOOL ] YUREK PARTITIONS Increasing / Decreasing / Default using easy tool V2.0

[Annabathina]

I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.

1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partition Increaser.bet " file

7. Press ENTER key

8. NOW changes will starts

Note : Don't disconnect DEVICE until tool says SUCCESSFUL

9. Copy all the files which are present in " Partition_Increaser_and_Decreaser_for_tomato / files ........ and save them in your pc for restoring to default partitions

NOTE : for every new cm based installation you have to do this steps


STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system .... and select repair or Change File System .... and select resize
STEP3 Reboot

Partition changer ( Increase / default ) : link

USEFUL LINKS

ADB for pc : link

YU usb drivers : link

PdaNet drivers : link

@I Putu Tirta Agung S

YU YUREKA
YU YUREKA PLUS​

XDA:DevDB Information
[MOD / TOOL ] YUREK PARTITIONS Increasing / Decreasing / Default using easy tool V2.0, Tool/Utility for the YU Yureka

Contributors
Annabathina

Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-06-13
Current Beta Version: 1.0
Beta Release Date: 2016-06-09

Created 2016-06-13
Last Updated 2016-09-27

 

[Annabathina]

Reserved

Revert Back to default partition values

1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partitions to default.bet " file

NOTE : Don't disconnect device until tool says successful

7. After successfull device will boot in to TWRP
8. Go to wipe / Advance wipe
9. Select all except MICRO SD-CARE
10. Go to wipe / Advance wipe .... and select system .... and select repair or Change File System .... and select resize

11. Do this for all except Micro SD-card
12. After this you have to flash COS12.1 in fastboot mode [ very important ]
13. After setup os cos12.1 is complete
14. Unlock bootloader
15. flash TWRP

 

[Annabathina]

Reserved

Repair tomato if brick using @Annabathina tool
Then here is the solution for it ....

1. make sure that drivers are installed correctly
2. Connect to PC in " Normal mode " or " in recovery mode "
3. Open repair tool v 1.0
4. Open " repair tomato "

*********************** Note ****************************************

5. If tool says successful then device will boot in to TWRP , know wipe every thing including Internal sd card for 2 times

6. After this you have to flash COS12.1 in fastboot mode [ very important ]
7. After setup os cos12.1 is complete
8. Unlock bootloader
9. flash TWRP

Repair tomato if brick : link

 

[Annabathina]

 

[m0han]

......NOTE : For every new CM based installation you have to do...
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system ....
.......... and select repair or Change File System .... and select resize
STEP3 Reboot
NOTE: The above 3 STEPS are not required for MY roms ......

...5. If tool says successfull then wipe every thing including Internal sd card
6. If you are restoring older rom then you have to restore it for " 2 times "
7. After that go to wip / advance wip
8. select system........... repair or Change File System .... and select resize
9. select data ............repair or Change File System .... and select resize
10. cache .................repair or Change File System .... and select resize
11. reboot your device...

i) after resizing partitions, can i restore my nandroid backup?
ii) if yes, how many times should i restore a recent rom (r46)?
iii) just to re-confirm: is the above resizing step required for your new ownrom3.0?
iv) although you mention only system in your op, is it recommended to wipe system, data and cache?
i wanna try your tool and get larger partitions. please DO REPLY and help. thanks in advance.

 

[m0han]

......NOTE : For every new CM based installation you have to do...
STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system ....
.......... and select repair or Change File System .... and select resize
STEP3 Reboot
NOTE: The above 3 STEPS are not required for MY roms ......

...5. If tool says successfull then wipe every thing including Internal sd card
6. If you are restoring older rom then you have to restore it for " 2 times "
7. After that go to wip / advance wip
8. select system........... repair or Change File System .... and select resize
9. select data ............repair or Change File System .... and select resize
10. cache .................repair or Change File System .... and select resize
11. reboot your device...

i) after resizing partitions, can i restore my nandroid backup?
ii) if yes, how many times should i restore a recent rom (r46)?
iii) just to re-confirm: is the above resizing step required for your new ownrom3.0?
iv) although you mention only system in your op, is it recommended to wipe system, data and cache?
i wanna try your tool and get larger partitions. please DO REPLY and help. thanks in advance.

Yes
I don't get this question? What do you mean by this?
You can use any rom after rezising.
Yes, it is better to do a complete wipe after the process completed via TWRP

ok
"If you are restoring older rom then you have to restore it for " 2 times " (check the hidden quotes). hence the doubt.
"The above 3 STEPS are not required for MY roms" (check the hidden quotes). i mistakenly thought that ownrom release was his.
ok

thank you.

 

[Dibesh16]

I think I did some mistake now my in my phones file manager when i click on internal storage it says 'the file or folder was not found' and I dont have that much files like in this image as you said.......can you please provide the files

 

[elaiyabharathi.]

recovery

which recovery r u using....and plzz give a link and guide

 

[Annabathina]

I think I did some mistake now my in my phones file manager when i click on internal storage it says 'the file or folder was not found' and I dont have that much files like in this image as you said.......can you please provide the files

Go to OP 3rd poast for it

 

[poran123]

can anyone explain about this?? is this really required for flashing cm13 or any rom?? or without this also we can flash any cm13 rom?

 

[manthanshah16]

I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.

1. Unlocked bootloader and rooted device
2. Enable USB DEBUGGING
3. Make sure that device drivers are successfully installed
4. Connect to PC
5. Download Partition increased tool from download section
6. Click on " Partition Increaser.bet " file

7. Press ENTER key

8. NOW changes will starts

Note : Don't disconnect DEVICE until tool says SUCCESSFUL

9. Copy all the files which are present in " Partition_Increaser_and_Decreaser_for_tomato / files ........ and save them in your pc for restoring to default partitions

NOTE : for every new cm based installation you have to do this steps


STEP 1 flash any CM based rom
STEP2 after successfully flash go to wipe / advance wipe...and select system .... and select repair or Change File System .... and select resize
STEP3 Reboot

Partition changer ( Increase / default ) : link

USEFUL LINKS

ADB for pc : link

YU usb drivers : link

PdaNet drivers : link

@I Putu Tirta Agung S

YU YUREKA
YU YUREKA PLUS​

XDA:DevDB Information
[MOD / TOOL ] Tomat PARTITIONS Increasing / Decreasing / Default using easy tool V2.0, Tool/Utility for the YU Yureka

Contributors
Annabathina

Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-06-13
Current Beta Version: 1.0
Beta Release Date: 2016-06-09

Created 2016-06-13
Last Updated 2016-06-13

Bro can you help me with below issue ?
Suddenly my Yuphoria crashed and when tried to restart it is getting stuck on YU Logo.
able to go to fastboot mode and tried to flash latest official fast boot images using factory tools but it is unable flash and unable to mount /system /data and /cache partitions.
as per guide from some of the threads , tried boot to TWRP and tried to repair or wipe partitions but it is giving same error and unable to mount those partition. even tried to change file system-type and that too didn't help (ext4, fat etc)
in TWRP went to mount option and there it is showing 0mb for internal storage.
tried to manually mount using terminal (using commands like make_ext4fs) but that also didnt help.
Boot and recovery partitions are safe !
check attached images for more reference.
I think i have lost partitions or internal memory is corrupted ! if partitions are lost or corrupted anyway to rebuild or any other was to fix it ?
please please please someone help !

 

[Annabathina]

Bro can you help me with below issue ?
Suddenly my Yuphoria crashed and when tried to restart it is getting stuck on YU Logo.
able to go to fastboot mode and tried to flash latest official fast boot images using factory tools but it is unable flash and unable to mount /system /data and /cache partitions.
as per guide from some of the threads , tried boot to TWRP and tried to repair or wipe partitions but it is giving same error and unable to mount those partition. even tried to change file system-type and that too didn't help (ext4, fat etc)
in TWRP went to mount option and there it is showing 0mb for internal storage.
tried to manually mount using terminal (using commands like make_ext4fs) but that also didnt help.
Boot and recovery partitions are safe !
check attached images for more reference.
I think i have lost partitions or internal memory is corrupted ! if partitions are lost or corrupted anyway to rebuild or any other was to fix it ?
please please please someone help !

Hey MAN your not even reading THREAD TITLE
this tool is for YUREKA [tomato]

 

[manthanshah16]

Hey MAN your not even reading THREAD TITLE
this tool is for YUREKA [tomato]

ya i know but thought of just checking.. u might have solution or tool for yuphoria !

 

[Annabathina]

ya i know but thought of just checking.. u might have solution or tool for yuphoria !

I have developed this tool for YUREKA only bucz in YU devices I am using YUREKA

and without devices it is very hard to build a tool like this

 

[Byyt]

Getting error message in recovery.

I'm able to repartition successfully but when I resize the system partition in TWRP after flashing stock CM13, I get this message:
"/sbin/resize2fs /dev/block/mmcblk0p25 process ended with ERROR: 1
Unable to resize system."
Tried multiple times. Didn't work.

 

[Bhavesh_khatri]

Mention repartition size

Please metion the repartition size after running you tool.

 

[Bhavesh_khatri]

I did it the size increased. But after flashing rom it again restored to default size. The change was temporary before installing rom. Phone is rooted and tried 6 to 7 times, why does this happens???

 

[yogdigit]

Done Successfully: Best Tool

I am used your tool to increase system space and done successfully few days ago, I am on CrDroid 7.1 (2.0 Version), want to upgrade 2.2 version, do I need to resize system space again?

As per crDroid Upgrading Process from earlier version of crDroid:

- Copy crDroid ZIP to your internal SDCard
- Boot into Recovery
- Wipe system and cache
- Flash crDroid zip
- Flash Gapps
- Reboot

 

[balaji00710]

i have an issue while formatting userdata....
i tried too many times but i cant able to format the userdata...
can you please help me to solve this issue...

 

[mankum93]

ROM is resetting the partitions made by your tool.

Hi,

First of all, I thank you from the bottom of my heart for having written an awesome tool. I employed this tool and have been able to successfully repartition my Yureka device to 2.5GB system.

Background:
Its been long since Cyanogen died and I was looking forward to migrate to a newer ROM. Turns out, Resurrection Remix has a custom ROM for Tomato with Nougat support: sourceforge.net/projects/resurrectionremix/files/tomato/
courtesy being of Mr Abhishek, the maintainer of ROM for Yureka.

Anyway, I went ahead, changed my recovery from Cyanogen to TeamWin and flashed the new ROM, the only part remaining being flashing of GApps except flashing GApps gave me the infamous Error 70 : tech.chandrahasa.com/2017/03/09/error-70-gapps-fix/

In my case, I wanted to repartition /system to fix the problem and so used your tool to do that. It worked and it ended up formatting /system, /dalvik, /cache, /data.

Problem:
When I checked the partition size, it showed 2.5GB just as you promised at this point. I went ahead and flashed the new ROM and somehow, the partition ended up being 1.15 GB like it was there originally. I suspect the install script of the ROM resets the partition size as a sanity check by default after all, the ROM is a fork of the CM 12.1 ROM that originally came up with the phone.

Question:
How can I keep this new repartition size and prevent the ROM from resetting it to 1.15GB(if indeed that's the case)?

For your reference,

Here is the Update script for the ROM:

assert(getprop("ro.product.device") == "YUREKA" || getprop("ro.build.product") == "YUREKA" || abort("E3004: This package is for device: YUREKA; this device is " + getprop("ro.product.device") + "."););
assert(cm.verify_trustzone("TZ.BF.3.0.R2-00034") == "1");
ui_print("Target: YU/YUREKA/YUREKA:5.1.1/LMY49J/YOG4PAS8A4:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
ui_print(" ");
ui_print(" ");
ui_print(" ");
ui_print(" RRRRRRRRRRRRRRRRR     RRRRRRRRRRRRRRRRR   ");
ui_print(" R::::::::::::::::R    R::::::::::::::::R  ");
ui_print(" R::::::RRRRRR:::::R   R::::::RRRRRR:::::R ");
ui_print(" RR:::::R     R:::::R  RR:::::R     R:::::R");
ui_print("   R::::R     R:::::R    R::::R     R:::::R");
ui_print("   R::::R     R:::::R    R::::R     R:::::R");
ui_print("   R::::RRRRRR:::::R     R::::RRRRRR:::::R ");
ui_print("   R:::::::::::::RR      R:::::::::::::RR  ");
ui_print("   R::::RRRRRR:::::R     R::::RRRRRR:::::R ");
ui_print("   R::::R     R:::::R    R::::R     R:::::R");
ui_print("   R::::R     R:::::R    R::::R     R:::::R");
ui_print("   R::::R     R:::::R    R::::R     R:::::R");
ui_print(" RR:::::R     R:::::R  RR:::::R     R:::::R");
ui_print(" R::::::R     R:::::R  R::::::R     R:::::R");
ui_print(" R::::::R     R:::::R  R::::::R     R:::::R");
ui_print(" RRRRRRRR     RRRRRRR  RRRRRRRR     RRRRRRR");
ui_print(" ");
ui_print(" ");
ui_print(" **************** Software *****************");
ui_print(" OS ver: RR-N-v5.8.3-20170621-tomato-OFFICIAL-VoLTE");
ui_print("");
ui_print(" Android ver: 7.1.2");
ui_print("");
ui_print(" Security patch: 2017-06-05");
ui_print("");
ui_print(" SDK ver: 25");
ui_print("");
ui_print(" Root status: Enabled");
ui_print("");
ui_print(" Build ID: NJH47B");
ui_print("");
ui_print(" Build date: Wed Jun 21 18:23:54 IST 2017");
ui_print("");
ui_print(" Build type: OFFICIAL-VoLTE");
ui_print("");
ui_print(" Build host: DeadlyMachine");
ui_print("");
ui_print(" Maintainer: Men_in_black007");
ui_print(" **************** Hardware *****************");
ui_print(" Device codename: tomato");
ui_print("");
ui_print(" Manufacturer: YU");
ui_print("");
ui_print(" *******************************************");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("f2fs", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
  abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);